When placing an unfillable hold the screen will not advance on the override if there is no items

Bug #1906842 reported by Steve Callender
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Evergreen
Fix Released
Medium
Unassigned
3.7
Fix Released
Medium
Unassigned

Bug Description

Tested on 3.3, 3.4, 3.5, 3.6

When placing an unfillable hold with the PLACE_UNFILLABLE_HOLD permission (may need the ITEM_NOT_HOLDABLE.override permission as well) the override will appear, but when forcing the override the screen will not advance and will remain on the override screen.

There was an earlier issue where this was fixed, but it was for if there was a potential item that was not-holdable.

This issue happens when there are absolutely no items available for the hold, such as using a pickup library that doesn't have the title and has their hard boundary set to 1.

Potential patch incoming.

Steve

Revision history for this message
Steve Callender (stevecallender) wrote :
Changed in evergreen:
importance: Undecided → Medium
status: New → Confirmed
tags: added: holds
Changed in evergreen:
assignee: nobody → Terran McCanna (tmccanna)
Revision history for this message
Terran McCanna (tmccanna) wrote :

Noting that this solves the problem with the traditional staff catalog, but there is still an issue with the angular staff catalog that I suspect is in the angular logic rather than the perl logic - I'll open a separate bug for that.

My sign off for this one is at:

https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/mccanna/lp1906842_unfillable_hold_perm_fix_signoff

tags: added: pullrequest
tags: added: signedoff
Changed in evergreen:
assignee: Terran McCanna (tmccanna) → nobody
Dan Briem (dbriem)
tags: added: circ-holds
removed: holds
Michele Morgan (mmorgan)
Changed in evergreen:
milestone: none → 3.7.3
Revision history for this message
Galen Charlton (gmc) wrote :

Pushed down to rel_3_7. Thanks, Mike, Steve, and Terran!

Changed in evergreen:
milestone: 3.7.3 → 3.8.1
no longer affects: evergreen/3.6
Changed in evergreen:
status: Confirmed → Fix Committed
Changed in evergreen:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.