Bug 22727 - Forgiven fines are recreated when lost item that was not marked returned is returned
Summary: Forgiven fines are recreated when lost item that was not marked returned is r...
Status: RESOLVED DUPLICATE of bug 22877
Alias: None
Product: Koha
Classification: Unclassified
Component: Fines and fees (show other bugs)
Version: Main
Hardware: All All
: P5 - low normal (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-17 17:26 UTC by Nick Clemens
Modified: 2019-06-10 17:59 UTC (History)
12 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Clemens 2019-04-17 17:26:20 UTC
This was a dsicvoery that Koha works this way, and has for some time, but goes against what we had believed happened.  This is not necessarily undesired behaviour, however, it should probably be a choice (charge/do not charge overdue fines when lost item returned if fines previously forgiven)

Filing for discussion.

To recreate:
1 - Setup:
      FinesMode: Calculate and charge (production)
      WhenLostForgiveFine: Forgive
      MarkLostItemsAsReturned: Select none
      Make sure your circ rules include fines
      Find an item with a replacement cost
2 - Backdate a checkout to a patron with the item from above
3 - Run fines.pl  - patron gets charges
4 - Mark the item lost, it is not returned, fines are forgiven, patron is charged replacement
5 - Return the item
6 - Patron gets a new fine for the overdue with the same amount that was forgiven
Comment 1 Andrew Fuerste-Henry 2019-04-17 18:02:20 UTC
Agreeing with Nick that the bug here is not that the fine reappears but, rather, that we don't have a choice about whether or not the fine reappears. Some libraries very much want this, others very much do not.
Comment 2 Andrew Fuerste-Henry 2019-06-10 17:59:57 UTC

*** This bug has been marked as a duplicate of bug 22877 ***