https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29161 Andrew Fuerste-Henry <andrew@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andrew@bywatersolutions.com Severity|enhancement |normal --- Comment #1 from Andrew Fuerste-Henry <andrew@bywatersolutions.com> --- Changing this from Enhancement to Normal, as it is legitimately a bug rather than an enhancement. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29161 --- Comment #3 from Nick Clemens <nick@bywatersolutions.com> --- Created attachment 128171 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=128171&action=edit Bug 29161: POC This is messy - our listing of holds only grabs the first, so we cannot tell whether we have both itemnumber and biblionumber holds. This patch removes the limit on priority one, then checks in get_items_that_can_fill for both item level and title level holds. I don't know how this affects the grouping for display We also only deal with one hold at a time on this report - if there are several title level holds, we only see it once, I guess fine, you fill that, run the report, fill the second Test plan below fails To test: 1 - Place an item level hold on a biblio with multiple items 2 - Run Holds to pull 3 - The hold shgows - okay 4 - Checkout the item with the hold to another patron 5 - The holds shows - not okay 6 - Apply patch 7 - The hold no longer shows 8 - Place a title level hold 9 - That hold shows -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29161 Andrew Fuerste-Henry <andrew@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #4 from Andrew Fuerste-Henry <andrew@bywatersolutions.com> --- After some testing, this issue is a side effect of bug 29786. The patch there will correct this. *** This bug has been marked as a duplicate of bug 29786 *** -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.