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.
*** This bug has been marked as a duplicate of bug 30935 ***