Bug 29974 - Changing status of held item to Damaged can result in inaccurate hold status
Summary: Changing status of held item to Damaged can result in inaccurate hold status
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Circulation (show other bugs)
Version: 21.05
Hardware: All All
: P5 - low trivial (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-01-28 21:31 UTC by Sara Brown
Modified: 2023-03-09 15:31 UTC (History)
4 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sara Brown 2022-01-28 21:31:17 UTC
With AllowHoldsOnDamagedItems set to "don't allow", if an undamaged item is waiting on hold for a patron, has its Damaged status set while waiting, and then is checked out to the patron, Koha thinks the item is simultaneously still held and checked out.

To recreate:
-Place a hold on an undamaged item
-Trigger the hold
-Once the item is waiting for the patron, change its status to Damaged
-Check the item out to that patron

In the bib, the item now shows as both waiting and checked out in the holdings table and in the Holds tab as waiting. In the patron's record, it shows as checked out and waiting. It also still shows in 'Holds awaiting pickup'.
Comment 1 Christopher Brannon 2022-01-28 22:40:58 UTC
I can confirm.  We've run into this issue on more than one occasion.  Would like to see this fixed ASAP.
Comment 2 Katrin Fischer 2022-06-25 21:04:45 UTC
I guess this is the case because a 'damaged' item can no longer 'fill' the hold... but it's already waiting, so already triggered the hold. Maybe it could be changed for this case.

I just wonder if there could be other use cases where this behaviour could be wanted?