https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40529
Pedro Amorim <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |Patch doesn't apply --- Comment #24 from Pedro Amorim <[email protected]> --- (In reply to Andrew Fuerste-Henry from comment #23) > I hit one issue in testing here in steps 24/25, when I build the holds queue > while my test patron (Patron A) has grouped hold for which one hold is > Waiting and therefore the target of the group. > > With DisaplyAddHoldGroups enabled, the other holds in that group correctly > do not show in the Queue. However, if one of the bibs that is not the target > of the hold group has a second hold on it for another patron (Patron B), > that title shows in the holds queue as needing to be pulled for Patron A. > > Holds to Pull correctly shows that second title as needing to be pulled for > Patron B. > At checkin, the item correctly allocates to Patron B. > But the queue is incorrectly grabbing the patron from the first hold, even > though that hold should be fully skipped because it's not the target for its > group. Thank you Andrew, not applying for me currently. Taking a look at a rebase and then your comments. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
