Bug 31600 - Holds to pull displaying the patron for the last lowest priority hold instead of the first highest priority hold
Summary: Holds to pull displaying the patron for the last lowest priority hold instead...
Status: RESOLVED DUPLICATE of bug 30935
Alias: None
Product: Koha
Classification: Unclassified
Component: Hold requests (show other bugs)
Version: Main
Hardware: All All
: P5 - low normal
Assignee: Kyle M Hall (khall)
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-09-22 12:53 UTC by Kyle M Hall (khall)
Modified: 2022-09-22 13:06 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
Bug 31600: Holds to pull displaying the patron for the last lowest priority hold instead of the first highest priority hold (1.24 KB, patch)
2022-09-22 12:58 UTC, Kyle M Hall (khall)
Details | Diff | Splinter Review

Note You need to log in before you can comment on or make changes to this bug.
Description Kyle M Hall (khall) 2022-09-22 12:53:57 UTC
If there are holds on a record for patrons A, B and C with priorities 1, 2 and 3, the holds to pull report will display patron C even though patron A is most likely the patron the item will trap for.
Comment 1 Kyle M Hall (khall) 2022-09-22 12:58:19 UTC
Created attachment 140846 [details] [review]
Bug 31600: Holds to pull displaying the patron for the last lowest priority hold instead of the first highest priority hold

If there are holds on a record for patrons A, B and C with priorities 1, 2 and 3, the holds to pull report will display patron C even though patron A is most likely the patron the item will trap for.

Test Plan:
1) Place some holds on a record
2) View the holds to pull report
3) Note the patron listed is not the top priority hold
4) Apply this patch
5) Restart all the things!
6) Reload the page
7) You should now see the top priority patron listed!
Comment 2 Kyle M Hall (khall) 2022-09-22 13:06:09 UTC

*** This bug has been marked as a duplicate of bug 30935 ***