Deleting item with holds from catalog does not trigger Hold Cancelled Notification (No Target) notice
Bug #1984110 reported by
Lindsay Stratton
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
v3.8
With "Hold Cancelled Notification (Staff)" notice enabled, cancelling a hold from the patron account, from title record > view holds, and by cancelling acquisitions lineitems with copies triggers the notice as expected.
The notice is NOT triggered if an item (either single item or item/vol with item or volume hold, or last item/vol and bib with a title hold) is directly deleted, although deleting the holdings record does cancel the hold.
The expectation is that the notice would be triggered when a hold is cancelled by any staff action or interface.
Changed in evergreen: | |
status: | New → Confirmed |
status: | Confirmed → New |
tags: | added: cataloging circ-holds |
To post a comment you must log in.
I found this bug while testing cancellation notifications for the situation described above - when the last item on a bib with a hold is deleted.
This type of hold cancellation gets the cancel cause of "Untargeted Expiration", so the applicable action triggers are those with the hook: hold_request. cancel. expire_ no_target. The stock event definitions are "Hold Cancelled (No Target) Email Notification" and "Hold Cancelled (No Target) User Message".
I am not able to generate any notifications the (No Target) notifications enabled, so I'm marking this Confirmed, and taking the liberty of updating the bug Summary.