Summary: | Hard due date should block renewals when it wouldn't extend the due date | ||
---|---|---|---|
Product: | Koha | Reporter: | Lisette Scheer <lisettepalouse+koha> |
Component: | Circulation | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | cslone, gmcharlt, kyle.m.hall, lisettepalouse+koha |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: |
Description
Lisette Scheer
2019-05-17 19:07:29 UTC
Agreed that this causes a problem. We have just run into this with a patron. They renewed an item with an already passed hard due date via the OPAC. Koha didn't change the due date, but still assessed them a fine (and then reassessed a fine when the item was returned). To replicate: 1.) Set a circulation and fine rule up for an item type to have a hard due date. 2.) Check out the item with the due date manually set to, or just before, the hard due date. 3.) Renew the item (staff or OPAC), the due date will not be extended past the hard due date, though no warning before is given (or special indication after). |