We've been noticing that new items added to the collection do not honor the LocalHoldsPriority setting on the first trigger. It seems to catch on later.
More details on a failed LocalHoldsPriority:
Had an existing bib. Have a patron whose home library is A, but wanted to pickup at B. We bought another item for this bib. We added the item to library B, and then triggered the hold. It went on hold for a patron at library C.
LocalHoldsPriority is set to give priority for filling holds to patrons whose pickup library matches the item's home library.
*** This bug has been marked as a duplicate of bug 15516 ***
(In reply to Christopher Brannon from comment #2)
> *** This bug has been marked as a duplicate of bug 15516 ***
Sorry, not a duplicate. Wrong bug!
Can't seem to reproduce in a test environment. May not have all settings or conditions accounted for, but this may be resolved with https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14514. Going to mark this as a duplicate for now. Will reopen if the problem persists after that patch is released.
*** This bug has been marked as a duplicate of bug 14514 ***