[Koha-bugs] [Bug 20567] New: "Holds per record (count)" limit is not enforced after item is captured for hold

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

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20567

            Bug ID: 20567
           Summary: "Holds per record (count)" limit is not enforced after
                    item is captured for hold
 Change sponsored?: ---
           Product: Koha
           Version: 17.05
          Hardware: All
                OS: All
            Status: NEW
          Severity: minor
          Priority: P5 - low
         Component: Hold requests
          Assignee: koha-bugs at lists.koha-community.org
          Reporter: margaret at bywatersolutions.com
        QA Contact: testopia at bugs.koha-community.org
                CC: gmcharlt at gmail.com

Created attachment 74042
  -->
https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=74042&action=edit
Multiple holds on one item record in staff client

"Holds per record (count)" limit is not enforced after an item on the record is
captured for hold and moves from Pending to Waiting Pickup status. At this
point it is possible to place another hold on that record in violation of the
"Holds per record (count)" setting.

I was able to replicate this behavior with the following steps: 

1. Set "Holds per record (count)" to 1 for your patron category/item type rule 
2. Create a record and add at least two items, making sure the MARC and Item
Koha Item Type is filled in
3. Place a hold on the record for a patron 
4. Check in one of the items and confirm/transfer/capture the hold for the
patron 
5. Place a second hold on the same record for the same patron  

In either Staff or Opac the second hold on this bib is allowed after the first
hold moves to Waiting for Pickup status.

I think that this problem is very closely related to bugzilla 17978 and or
15404, but I did not see a specific mention of the "Holds per record (count)"
limit upon perusal of those bugs.

-- 
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.