https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36817 --- Comment #1 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- 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. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36817 --- Comment #3 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- 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. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36817 --- Comment #4 from Sara Brown <sbrown@bywatersolutions.com> --- 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). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36817 Emily Lamancusa <emily.lamancusa@montgomerycountymd.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |emily.lamancusa@montgomeryc | |ountymd.gov Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #5 from Emily Lamancusa <emily.lamancusa@montgomerycountymd.gov> --- *** This bug has been marked as a duplicate of bug 32565 *** -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.