Bug 5785

Summary: Holds should catch new acquisitions
Product: Koha Reporter: Jared Camins-Esakov <jcamins>
Component: Hold requestsAssignee: Kyle M Hall <kyle.m.hall>
Status: CLOSED FIXED QA Contact: Bugs List <koha-bugs>
Severity: enhancement    
Priority: P5 - low CC: amitddng135, gmcharlt, melia
Version: unspecified   
Hardware: All   
OS: All   
Change sponsored?: --- Patch complexity: ---
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:

Description Jared Camins-Esakov 2011-02-21 19:33:02 UTC
When a new item is added to a bib with bib-level holds, the holds system is not triggered by the new item, even though it should be (if the item type permits holds according to the circulation rules).
Comment 1 Katrin Fischer 2019-04-10 00:33:56 UTC
I am not sure about what was the intended behavior here. We display information about holds in acq. Once an item is ready for checkout, it's usually returned and triggers the hold. The checkin can also be used to remove a 'processing' status.

I am not sure when the hold should be caught otherwise - on receive would be too early as getting items ready might take a few days depending on workflows.
Comment 2 Katrin Fischer 2022-02-19 18:30:27 UTC
*** Bug 10440 has been marked as a duplicate of this bug. ***
Comment 3 Katrin Fischer 2023-01-07 23:26:15 UTC
I imagine Jared meant that the item should show up on the holds queue and I assume with RealTimeHoldsQueue it will now as every change to the record/items will trigger an update.

See:
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29346#c15