http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14380
Barton Chittenden <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #4 from Barton Chittenden <[email protected]> --- (In reply to Katrin Fischer from comment #3) > I think I disagree about the 'one line'. Once you renew the overdue process > restarts and is not in any way related to the first one, I'd avoid mixing > the data. It would make it really hard to see why the amount is as high as > it is. With the 2 different due dates you get a clear clue. > > I see a renewal more like a new checkout - only that Koha doesn't treat a > renewal as a new checkout as some other systems do (which is fine!). > > But I totally agree about the description being misused. > > I think we need to think about this a bit more and should note it as a use > case/test case we need to test and make sure works properly. Katrin, After discussion with Kyle Hall, I agree with you assessment: Closing the first fine and creating a new fine on renewal is standard behavior for Koha. This still leaves the issue of the second Fine not being closed. I'm going to mark the ticket as "RESOLVED/INVALID", and open a new ticket which specifically addresses the un-closed fine. I'll carry your comments regarding a test case forward to the new ticket. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
