https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41410 Andrew Fuerste-Henry <andrew@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Failed QA --- Comment #16 from Andrew Fuerste-Henry <andrew@bywatersolutions.com> --- It's possible to have the holds queue target an item that does not match the conditions defined for Local Holds Exclusivity but nonetheless gets flagged as a local_holdgroup_match. When this happens, staff are told via the queue to pull an item that will not trigger the hold at checkin. To reproduce: - Set LocalHoldsExclusivity to match hold pickup and item holdingbranch - Set LocalHoldsPriority to match patron home to item home - Make a hold group containing Fairfield and Fairview - Have a bib with 1 item at Fairview (both home and holding) and 1 item at Midway (both home and holding) - Place a hold on your bib for Henry Acevedo (patron home Midway) for pickup at Fairfield - build holds queue LocalHoldsPriority tells the queue to target the Midway item. That target gets erroneously marked as a local holdgroup match. If I turn off LocalHoldsPriority and use the transport cost matrix to make Koha target the Midway item instead of the Fairview item, it does not get marked as a local holdgroup match. -- You are receiving this mail because: You are watching all bug changes.