Bug 39687 - Changing status on waiting hold produces data issues
Summary: Changing status on waiting hold produces data issues
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Hold requests (show other bugs)
Version: Main
Hardware: All All
: P5 - low normal
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-04-18 23:14 UTC by Christopher Brannon
Modified: 2025-04-18 23:14 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Brannon 2025-04-18 23:14:31 UTC
To reproduce the problem:

1) Set AllowHoldsOnDamagedItems to Don't allow
2) Place an item on hold for patron
3) Mark it as in mending (damaged) (staff notice it needs repair when returned)
4) Patron picks up the item and it is checked out to the patron
5) Notice the item is checked out to the patron, but also showing in mending, and still waiting for that patron.

While some would say this could be avoided by workflow changes, it is still a data problem that leads to confusion for all involved.

I would suggest that 1) the hold waiting not allow status changes, or 2) the hold allow the waiting status to be changed for this scenario.  It seems that AllowHoldsOnDamagedItems should only block holds from being placed, not holds that are already waiting.  I don't think blocking the checkout of the item that is already waiting would be a good option because the patron has been notified that the item is already there.