[Koha-bugs] [Bug 21495] New: Regression in hold override functionality

[bugzilla-daemon at bugs.koha-community.org]

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: koha-bugs at lists.koha-community.org
          Reporter: stefan.berndtsson at ub.gu.se
        QA Contact: testopia at bugs.koha-community.org
                CC: gmcharlt at gmail.com

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.