Bug 12630: Prioritizing "Hold starts on date" -holds causes all other holds to be...
authorOlli-Antti Kivilahti <olli-antti.kivilahti@jns.fi>
Wed, 23 Jul 2014 05:41:47 +0000 (08:41 +0300)
committerLucas Gass <lucas@bywatersolutions.com>
Fri, 15 Jul 2022 17:37:01 +0000 (17:37 +0000)
commit8c509cf33029b376b9e426ede788c44654876b75
treebba41d99facf9457f8f5af982d1ea5a375108671
parentc3ffcda4614dccd57992d7460db277b80c9cdba0
Bug 12630: Prioritizing "Hold starts on date" -holds causes all other holds to be prioritized as well!

-------------------------
-- REPLICATE LIKE THIS --
-------------------------

0. Enable AllowHoldDateInFuture-system preference!

1. Select a biblio with some holds.
2. Place a hold with the "Hold starts on date"-attribute set to future.
3. More the specific hold up on the priority queue.
4. Add another normal hold, observe how it is prioritized with the "Hold starts on date"-hold, leaving old holds to the prioritization queue tail.

Unfair eh?

Signed-off-by: Kyle M Hall <kyle@bywatersolutions.com>
Signed-off-by: Jonathan Druart <jonathan.druart@biblibre.com>
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
(cherry picked from commit 05ac7e0d4a1d4247df43f4a83ead509cfaffa04c)

Signed-off-by: Lucas Gass <lucas@bywatersolutions.com>
C4/Reserves.pm