[Bug 15914] New: LocalHoldsPriority is not honored when new item is first triggered
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15914 Bug ID: 15914 Summary: LocalHoldsPriority is not honored when new item is first triggered Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs@lists.koha-community.org Reporter: cbrannon@cdalibrary.org QA Contact: testopia@bugs.koha-community.org CC: gmcharlt@gmail.com 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. Christopher -- 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=15914 --- Comment #1 from Christopher Brannon <cbrannon@cdalibrary.org> --- 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. Christopher -- 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=15914 Christopher Brannon <cbrannon@cdalibrary.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - low |P1 - high Severity|normal |major -- 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=15914 Christopher Brannon <cbrannon@cdalibrary.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #2 from Christopher Brannon <cbrannon@cdalibrary.org> --- *** This bug has been marked as a duplicate of bug 15516 *** -- 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=15914 Christopher Brannon <cbrannon@cdalibrary.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|DUPLICATE |--- Status|RESOLVED |REOPENED -- 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=15914 --- Comment #3 from Christopher Brannon <cbrannon@cdalibrary.org> --- (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! -- 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=15914 Christopher Brannon <cbrannon@cdalibrary.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DUPLICATE Status|REOPENED |RESOLVED --- Comment #4 from Christopher Brannon <cbrannon@cdalibrary.org> --- 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. Christopher *** This bug has been marked as a duplicate of bug 14514 *** -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
participants (1)
-
bugzilla-daemon＠bugs.koha-community.org