Bug 30857 - Add option make Non-Priority holds also automatically set to Lowest Priority
Summary: Add option make Non-Priority holds also automatically set to Lowest Priority
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Hold requests (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-05-26 15:48 UTC by Andrew Fuerste-Henry
Modified: 2022-05-26 15:48 UTC (History)
1 user (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Fuerste-Henry 2022-05-26 15:48:47 UTC
When placing a hold, one can check the Non-Priority box to make it so the hold will not block renewals for other patrons. (reserves.non_priority=1)

Once a hold is placed, one can click the arrow to Toggle Lowest Priority to make the hold stay at the bottom of the priority list. (reserves.lowestpriority=1)

These two features work so nicely together, I'd like to see a system preference that gives the option for checking the Non-Priority box at hold creation to automatically also set that hold to lowest priority.