[Koha-bugs] [Bug 21181] New: Cancel expired holds cronjob does not cancel holds in transit if ExpireReservesMaxPickUpDelay not set
bugzilla-daemon at bugs.koha-community.org
bugzilla-daemon at bugs.koha-community.org
Wed Aug 8 19:18:51 CEST 2018
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21181
Bug ID: 21181
Summary: Cancel expired holds cronjob does not cancel holds in
transit if ExpireReservesMaxPickUpDelay not set
Change sponsored?: ---
Product: Koha
Version: master
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P5 - low
Component: Command-line Utilities
Assignee: koha-bugs at lists.koha-community.org
Reporter: nick at bywatersolutions.com
QA Contact: testopia at bugs.koha-community.org
CC: robin at catalyst.net.nz
Debatable, but that problem as it arose:
1 - Patron places a hold, sets 'not needed after' to July 1
2 - Hold is put in transit
3 - Time passes, it is now July 2
4 - Cancel expired holds cron does not cancel hold - found='W'
5 - Hold arrives at destination on July 3
6 - Hold is trapped, patron is notified
--
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.
More information about the Koha-bugs
mailing list