Bug 31467 - Holds to pull page does not return the 'first patron' with the top priority hold
Summary: Holds to pull page does not return the 'first patron' with the top priority hold
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 enhancement (vote)
Assignee: Alex Buckley
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-08-25 23:33 UTC by Alex Buckley
Modified: 2022-08-25 23:36 UTC (History)
1 user (show)

See Also:
Change sponsored?: 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 Alex Buckley 2022-08-25 23:33:07 UTC
The functionality in bug 24488 of showing the correct 'first patron' details no longer always works. 

---

Here is an example of the current 'Holds to pull' page behaviour on master where one biblio has two biblio-level holds on it:

+------------+--------------+------------+----------------+----------+---------+-------------+---------------------+
| reserve_id | biblionumber | itemnumber | borrowernumber | priority | suspend | reservedate | timestamp           |
+------------+--------------+------------+----------------+----------+---------+-------------+---------------------+
|      17704 |        26454 |       NULL |           8450 |        1 |       0 | 2022-08-25  | 2022-08-25 15:16:34 |
|      17705 |        26454 |       NULL |           6998 |        2 |       0 | 2022-08-25  | 2022-08-25 15:17:22 |
+------------+--------------+------------+----------------+----------+---------+-------------+---------------------+

The 'Holds to pull' page should display borrower 8450 as the 'First patron', as they have a priority of 1. But it incorrectly displays borrower 6998, instead.

The 'Holds to pull' page should display the 'First patron' based on who has the top priority hold.
Comment 1 Alex Buckley 2022-08-25 23:36:30 UTC

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