[Koha-bugs] [Bug 32702] Item statuses that block holds should be checked in CanItemBeReserved

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Thu May 25 19:48:09 CEST 2023


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

Andrew Fuerste-Henry <andrewfh at dubcolib.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|Needs Signoff               |Failed QA
                 CC|                            |andrewfh at dubcolib.org

--- Comment #7 from Andrew Fuerste-Henry <andrewfh at dubcolib.org> ---
(In reply to Nick Clemens from comment #4)
> 
> To test:
> 1 - Setup a record with items to have:
>     1 available item
>     1 lost item
>     1 item with positive not for loan status
>     1 item with negative not for loan status
>     1 item withdrawn
>     1 item damaged
>     1 item not for loan by itemtype
> 2 - Attempt to place hold on staff and opac and note the statuses
> 3 - Apply patch
> 4 - Confirm the statuses have not changed
> 5 - Attempt to hold lost/damaged/withdrawn/notforloan items via API
> 6 - You should not be able to place the hold
> 7 - Attempt to place club holds on these items - it should not be possible
> 8 - Attempt to place holds via ILSDI - it should not be possible

With these patches applied, I was able to create holds via API for all of these
items, despite their statuses. I did get blocked from placing holds beyond the
holds-per-record limit in the circ rules, but otherwise everything was
permitted.

Also, after the patches, in the staff client the lost and withdrawn items are
showing new wording in the first column of the item selection table when
placing a hold.

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


More information about the Koha-bugs mailing list