https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42392 Bug ID: 42392 Summary: patron_expiration_date on holds is always enforced but never seen or updated Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs@lists.koha-community.org Reporter: andrew@bywatersolutions.com QA Contact: testopia@bugs.koha-community.org CC: gmcharlt@gmail.com, lisette@bywatersolutions.com, tomascohen@gmail.com When a hold is placed via the staff interface or the OPAC, if a "not needed after" date is supplied, that date gets written into both reserves.patron_expiration_date and reserves.expirationdate. The staff interface only shows the user the value in expirationdate. It can be edited or removed entirely. However, changes made here do not change the patron_expiration_date. The cancel_expired_holds cron will cancel a hold with a patron_expiration_date in the past even if expirationdate is null or in the future. This can result in the following scenario: - patron places a hold with an expiration date - patron changes their mind and asks staff to remove the expiration date - hold now shows a blank expiration date in the staff interface and the message "Never expires" on the OPAC - the original expiration date comes, hold is automatically cancelled - patron is sad and confused -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.