Expiration date remains null if a captured hold is released
Bug #1836807 reported by
Jessica Woolford
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
New
|
Undecided
|
Unassigned |
Bug Description
Evergreen version 3.1.11
If a hold is captured and then released due to the hold being retargeted or a canceled transit, the hold expire time remains null. We have over 500 holds in our system that are not canceled, captured, fulfilled, or suspended and have no expiration date. In the rare case that these old holds get triggered, it is confusing for library staff.
Based on IRC discussion, I think it would be fine for the hold to get the expiration date any new holds would get.
tags: |
added: circ-holds removed: holds |
To post a comment you must log in.
Dug up the original IRC convo, since a similar issue came up today: http:// irc.evergreen- ils.org/ evergreen/ 2019-07- 16#i_412410