Bug 6344 - Hold priority displayed incorrectly when "Toggle Lowest Priority" option is used
Summary: Hold priority displayed incorrectly when "Toggle Lowest Priority" option is used
Status: CLOSED WORKSFORME
Alias: None
Product: Koha
Classification: Unclassified
Component: Hold requests (show other bugs)
Version: master
Hardware: All All
: P5 - low normal (vote)
Assignee: Ian Walls
QA Contact: Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-16 15:09 UTC by Owen Leonard
Modified: 2020-01-06 20:14 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 Owen Leonard 2011-05-16 15:09:58 UTC
If I toggle the lowest priority on a hold to "pin" it to the bottom of a hold's priority list, any holds I place after that will be displayed as being of lower priority.

1. Place a hold.
2. Set that hold to "lowest priority."
3. Place another hold. This hold will appear below the first.

Running build_holds_queue.pl does not affect the appearance of the priorities.

Only after one of the holds has been fulfilled will the priorities display correctly.

4. Check in a copy of the on-hold title.
5. The item will be allocated for the correct patron (not the one "pinned" to the bottom of the list."
6. Confirm.

Now the hold list will appear correctly: The "pinned" hold will appear at the bottom.
Comment 1 Owen Leonard 2014-07-15 18:24:18 UTC
This bug is in master as of 3.17.00.009
Comment 2 Katrin Fischer 2015-06-06 21:30:26 UTC
Still valid.
Comment 3 Katrin Fischer 2019-03-16 10:44:28 UTC
This appears to have been fixed!