When an item is overdue and is renewed the fines that were assessed are removed. This is obviously not a desired behavior.
There is not a lot of information on this, I wonder if it's only true if you recalculate fines on return or if it is a problem with the fines script?
Currently testing. Here's one problematic situation. If RenewalPeriodBase is set to the "the old due date off the checkout" and the item is still overdue after renewing, Koha will close the current fine from "FU" to "F" and generate a new fine! The fine will be somewhat smaller ( since the due date has been pushed forward by X days ), but the fines still overlap and are essentially duplicate fines!
I cannot reproduce this issue on master, nor can I reproduce on 3.10.05 which is the version the reporter is running. I'm guessing my system settings are set the same as the reporters.
(In reply to Elliott Davis from comment #0) > When an item is overdue and is renewed the fines that were assessed are > removed. This is obviously not a desired behavior. We are facing the same issue. I think this bug doesn't really matter if you recalculate fines daily using the fines.pl cronjob, since when you renew, the fine has already been generated for the overdue period.
(In reply to Olli-Antti Kivilahti from comment #4) > (In reply to Elliott Davis from comment #0) > > When an item is overdue and is renewed the fines that were assessed are > > removed. This is obviously not a desired behavior. > > We are facing the same issue. > I think this bug doesn't really matter if you recalculate fines daily using > the fines.pl cronjob, since when you renew, the fine has already been > generated for the overdue period. Hm, I think that is only partially correct. I think it would not touch the fine as long as the item doesn't get overdue again, but it will be a problem when it does get overdue agan. The fines would be recalculated from the new due date. I am not sure if this will be done as a new line in accuntlines or updating the old one. Maybe worth testing out.
I can confirm this on 3.18.4. Some pertinent settings are: CalculateFinesOnReturn: Do finesCalendar: Calculate fines based on days overdue not including days the library is closed
*** This bug has been marked as a duplicate of bug 14390 ***