https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24376
--- Comment #10 from Martin Renvoize <[email protected]> --- To clarify that a little.. Existing states: [%- CASE 'UNRETURNED' -%]<span> (Accruing)</span> # Set when fine is first created and still accruing [%- CASE 'RETURNED' -%]<span> (Returned)</span> # Set in C4::Circulation::AddReturn (can be called via AddIssue) [%- CASE 'RENEWED' -%]<span> (Renewed)</span> # Set in C4::Circulation::AddRenewal (can be called via AddIssue, but seldom is) [%- CASE 'REPLACED' -%]<span> (Replaced)</span> # [%- CASE 'REFUNDED' -%]<span> (Refunded)</span> # [%- CASE 'FORGIVEN' -%]<span> (Forgiven)</span> # Inside _FixOverduesOnReturn, if 'exemptfine' is true [%- CASE 'VOID' -%]<span> (Voided)</span> # [%- CASE 'LOST' -%]<span> (Lost)</span> # Set in C4::Circulation::LostItem (if WhenLostForgiveFine is disabled) I think it would make sense to reduce that list to `ACCRUING` and `FIXED` for overdues that are unpaid.. and then allow for 'FORGIVEN', 'VOID', and 'PAID' to signify 'payment' actions on the lines. This may have a knock on effect with our WhenLostForgiveFine handling if the item is subsequently found and returned.. I believe there's another bug already discussing that case however. -- 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] https://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/
