Hold targeter ignoring closed settings when only local copies
Bug #1868837 reported by
Steve Callender
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Won't Fix
|
Undecided
|
Unassigned | ||
3.6 |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
I found a situation where the hold targeter would ignore the circ.holds.
The code looks like it was creating a list of closed org units based on potential items, and removing out the local org unit in order to have a secondary settings check for the pickup library. If there were no outside org units to check first due to no outside copies, it would just skip the whole subroutine and never apply the second setting.
I believe this patch should address that. Thank you Mike Rylander for the eyes on this.
tags: | added: holds |
Changed in evergreen: | |
milestone: | none → 3.6.1 |
Changed in evergreen: | |
milestone: | 3.6.1 → 3.6.2 |
Changed in evergreen: | |
milestone: | 3.6.2 → 3.6.3 |
Changed in evergreen: | |
milestone: | 3.6.3 → 3.6.4 |
Changed in evergreen: | |
milestone: | 3.6.4 → 3.7.2 |
Changed in evergreen: | |
milestone: | 3.7.2 → none |
To post a comment you must log in.
Just a follow-up, I've seen this probably come up many times now.
The symptom is, if you are closed or all your branches are closed, and you are set to not process holds during closed times, but yet you are still occasionally seeing a random item pop up on the pull list, this is more than likely the bug you are hitting.