Retargeting a cancelled hold can cause problems with uncancelled captured holds

Bug #1469287 reported by Michele Morgan
This bug affects 2 people
Affects Status Importance Assigned to Milestone

Bug Description

When viewing a patron's cancelled holds, it is possible to select a hold and choose "Find Another Target" from the actions menu.

Since cancelled holds retain the value in the current_copy field, it's possible for another captured hold also to reference the same copy.

Retargeting the cancelled hold will change the status of the currently captured item.

Steps to reproduce:

-Place two holds on a record for different patrons, Patron A and Patron B.

-Check in the item to capture the hold for Patron A. Item is On holds shelf.

-Cancel the hold for the captured item.

-Check in the item to capture the hold for Patron B. Item in On holds shelf.

-Retrieve Patron A and view the patron's cancelled holds.

-Select the hold and choose Find another target from the Actions menu.

-The item's status will now be Reshelving.

-Patron A's hold will show Hold Status -1

A straighforward fix would be to not allow cancelled holds to be retargeted.

Revision history for this message
Erica Rohlfs (erohlfs) wrote :

Confirmed in version 2.8.1.

Changed in evergreen:
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
Andrea Neiman (aneiman) wrote :

Using the steps Michele described, I am not able to reproduce this in the web client v 3.2.1. The cancelled hold for Patron A shows as status = cancelled, as I would expect.

tags: added: fixedinwebby
Revision history for this message
Rogan Hamby (rogan-hamby) wrote :

I agree that we shouldn't allow canceled holds to be retargeted (or appear to) but I can't duplicate the behavior following these steps as of current master. The item's status remains on holds shelf and the hold does still show as canceled.

Revision history for this message
Rogan Hamby (rogan-hamby) wrote :

After some more thought given that between 2018 to now we can't replicate it I'm going to mark this one invalid though if someone else can replicate it I'd be curious about the circumstances.

Changed in evergreen:
status: Confirmed → Invalid
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.