[Koha-bugs] [Bug 31467] New: Holds to pull page does not return the 'first patron' with the top priority hold

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31467

            Bug ID: 31467
           Summary: Holds to pull page does not return the 'first patron'
                    with the top priority hold
 Change sponsored?: ---
           Product: Koha
           Version: master
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P5 - low
         Component: Hold requests
          Assignee: koha-bugs at lists.koha-community.org
          Reporter: alexbuckley at catalyst.net.nz
        QA Contact: testopia at bugs.koha-community.org
                CC: gmcharlt at gmail.com

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.

-- 
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.