https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42524
--- Comment #15 from Kristi Krueger <[email protected]> --- Veering off the test plan, sharing what I have looked at with this patch in a sandbox: Bib-level holds: 1. On 6/18 place three record-level holds each on 4 bibs (15, 52, 123, 53) 2. On 6/19 place two record-level holds each on the same 4 bibs. 3. Without changing HoldPriorityWhenMoved (set at last priority) moved 2 records from 6/18 and one from 6/19 from bib 15 to 123. The holds appended to the end of the existing hold priority. The display was by hold priority 1-8. 4. Changed HoldPriorityWhenMoved to ReserveDate 5. Moved 4 holds, 2 from 6/18 and two from 6/19 from bib 52 to 53. The holds filed in order by date placed (Great!) Item-level holds: 1. On 6/26 place two item-level holds on each of 4 bibs (1/ barcode 3999900000001, 8/39999000000313, 6/39999000000238, 12/39999000000511). 2. On 6/29, place two item-level holds on each of these barcodes. 3. Without changing HoldPriorityWhenMoved (set at last priority) moved 3 item-level holds from 3999900000001 to 39999000000313. The holds appended to the end of the existing hold priority, but the display was by date placed, with the hold priority out of order (see screenshot HoldPriority_DisplayByDate.png) 4. Changed HoldPriorityWhenMoved to ReserveDate. 5. Moved 3 item-level holds from 39999000000238 to 39999000000511. The holds filed in order by date placed (Great!) -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
