Bug 15914 - LocalHoldsPriority is not honored when new item is first triggered
Summary: LocalHoldsPriority is not honored when new item is first triggered
Status: RESOLVED DUPLICATE of bug 14514
Alias: None
Product: Koha
Classification: Unclassified
Component: Hold requests (show other bugs)
Version: unspecified
Hardware: All All
: P1 - high major
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-24 22:50 UTC by Christopher Brannon
Modified: 2016-03-24 21:52 UTC (History)
1 user (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Brannon 2016-02-24 22:50:13 UTC 
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
Comment 1 Christopher Brannon 2016-02-24 23:13:33 UTC 
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
Comment 2 Christopher Brannon 2016-03-21 22:56:19 UTC 

*** This bug has been marked as a duplicate of bug 15516 ***
Comment 3 Christopher Brannon 2016-03-21 22:57:22 UTC 
(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!
Comment 4 Christopher Brannon 2016-03-24 21:52:41 UTC 
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 ***