Bug 36817 - Holds with start date not appearing in holds queue
Summary: Holds with start date not appearing in holds queue
Status: RESOLVED DUPLICATE of bug 32565
Alias: None
Product: Koha
Classification: Unclassified
Component: Hold requests (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-05-08 14:14 UTC by Sara Brown
Modified: 2024-05-14 19:07 UTC (History)
2 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sara Brown 2024-05-08 14:14:45 UTC
Holds set with a start date 1 or more days in the future are not appearing on the holds queue on their start dates. This is for 23.05.10 for libraries using the real-time holds queue. (Test in progress for a library not using RTHQ.) The holds do appear on their start dates in holds to pull.
Comment 1 Katrin Fischer 2024-05-08 17:17:48 UTC
Hi Sara, can you explain the use case? For me this behavior sounds correct as I understand a hold is not "active" until its start date.
Comment 2 Sara Brown 2024-05-08 18:05:07 UTC
I'm sorry; I didn't explain it well originally. On the start date, the hold still isn't appearing in the queue.
Comment 3 Katrin Fischer 2024-05-08 18:14:44 UTC
OK, that makes sense. I think there is a bug that might help with that too, but I haven't tested:

Bug 32565 - Holds placed when all libraries are closed do not get added to holds queue if HoldsQueueSkipClosed and RealTimeHoldsQueue are enabled

The problem is that at the time the hold is placed it's rightfully not added to the queue by RTHQ. But then later it needs the cron to show up. This new switch only looks for "unallocated" holds (not yet in the holds queue) to add them.
Comment 4 Sara Brown 2024-05-08 18:19:31 UTC
Ah, that makes sense. And I hit enter on that comment too early:

The library's original use case was a staff member placing holds with start dates for an upcoming storytime. They placed the holds about 2 weeks ahead of actually needing the items but found that when the start date came, the holds were only visible on holds to pull (which they don't typically use).
Comment 5 Emily Lamancusa 2024-05-14 19:07:55 UTC

*** This bug has been marked as a duplicate of bug 32565 ***