Bug 28788 - Default holds policy by item type can be overridden but holds will not capture
Summary: Default holds policy by item type can be overridden but holds will not capture
Status: RESOLVED DUPLICATE of bug 20955
Alias: None
Product: Koha
Classification: Unclassified
Component: Hold requests (show other bugs)
Version: 20.05
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on: 31169
Blocks:
  Show dependency treegraph
 
Reported: 2021-07-30 16:51 UTC by Michael Adamyk
Modified: 2023-10-03 14:36 UTC (History)
2 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 Michael Adamyk 2021-07-30 16:51:00 UTC
If there are circulation rules in place preventing holds via the "Default holds policy by item type," intranet users with hold override permissions may still place holds outside these rules by ignoring the warning message. 

However, the hold itself is never captured. It will not appear on any library hold queues, and does not appear to exist until the item in question is checked in. At that point, the hold reappears and tries to fulfill itself. Because the hold never appeared before this, there was no way to know that the item should be checked in.

Holds violating the Default holds policy by item type should be either fully forbidden or they should function like normal holds when an override is given.
Comment 1 Emily Lamancusa 2023-10-03 14:36:07 UTC

*** This bug has been marked as a duplicate of bug 20955 ***