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)
committerArthur Suzuki <arthur.suzuki@biblibre.com>
Thu, 21 Jul 2022 13:51:16 +0000 (15:51 +0200)
commit22468b3061e9fab6c931931764487da59ddda5d3
tree7d399789961fcfdc9f40f4693823067a624c33f4
parent1259c2bfaab08b80cae7fa6f07983bf846819607
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>
(cherry picked from commit 8c509cf33029b376b9e426ede788c44654876b75)
Signed-off-by: Arthur Suzuki <arthur.suzuki@biblibre.com>
C4/Reserves.pm