https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21495
Bug ID: 21495
Summary: Regression in hold override functionality
Change sponsored?: ---
Product: Koha
Version: master
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P5 - low
Component: Hold requests
Assignee: [email protected]
Reporter: [email protected]
QA Contact: [email protected]
CC: [email protected]
The changes made by Bug 11512 causes regression in functionality. That change
assumes it is safe to override only tooManyReserves because other holds will
not be filled anyway.
[The rest is copied from Comment 14 in the bug, explaining our usecase]
>From what I can see in the code, this isn't actually true. CheckReserves does
not include neither LOST nor WITHDRAWN in its checks. In fact, we use the LOST
part here in Gothenburg.
When longoverdue.pl marks a book as LOST, our staff adds a reserve to that
item, so that they will be notified if it is returned. With the code prior to
this patch,
this works perfectly fine since we have the AllowHoldPolicyOverride set and
returning a LOST item fills the hold.
The same logic applies to WITHDRAWN.
--
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.
_______________________________________________
Koha-bugs mailing list
[email protected]
http://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/
