[Bug 30381] New: On order items still available for item level holds with TrapHoldsOnOrder
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30381 Bug ID: 30381 Summary: On order items still available for item level holds with TrapHoldsOnOrder Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Hold requests Assignee: koha-bugs@lists.koha-community.org Reporter: katrin.fischer@bsz-bw.de QA Contact: testopia@bugs.koha-community.org CC: gmcharlt@gmail.com When TrapHoldsOnOrder is set to not trap holds with negative not for loan status, it's still possible to place an item level hold on these items in the OPAC. To test: - Create an item with not for loan -1 = on order - Set OPAC item level holds to 'Force' for its itemtype in circulation conditions - Try to place a hold on it from the OPAC - Notice that a checkbox to select the item displays and you can place a hold -- 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=30381 Kyle M Hall <kyle@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kyle@bywatersolutions.com --- Comment #1 from Kyle M Hall <kyle@bywatersolutions.com> --- I don't think this is a bug. This syspref is not related to whether an item may be placed on hold or not. It is specifically constrained to only deciding if on order items can be trapped to filled existing holds. -- 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=30381 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|NEW |RESOLVED --- Comment #2 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- (In reply to Kyle M Hall from comment #1)
I don't think this is a bug. This syspref is not related to whether an item may be placed on hold or not. It is specifically constrained to only deciding if on order items can be trapped to filled existing holds.
Hi Kyle, I am still confused a bit by placing holds on items that will not trap... but for on order it probably makes the most sense as they will someday probably 'trap' when they become available. Thx. In case you know: How to handle it if libraries don't want the on order items to be already holdable? Using an itemtype is not really nice there, but the only thing I can think of right now. -- 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