Bug 26072

Summary: Add ability to *not* force holds to be placed via the REST API even if AllowHoldPolicyOverride is enabled
Product: Koha Reporter: Kyle M Hall <kyle>
Component: REST APIAssignee: Kyle M Hall <kyle>
Status: CLOSED INVALID QA Contact:
Severity: minor    
Priority: P5 - low    
Version: master   
Hardware: All   
OS: All   
See Also: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26181
Change sponsored?: --- Patch complexity: ---
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:
Attachments: Bug 26072: Add ability to *not* force holds to be placed via the REST API even if AllowHoldPolicyOverride is enabled

Description Kyle M Hall 2020-07-27 18:16:23 UTC
There are use cases where we need to be able to place holds via the API, but not place holds that are in violation of the current holds policy. If AllowHoldPolicyOverride is enabled, holds placed via the API will succeed regardless of violations of the current hold rules.
Comment 1 Kyle M Hall 2020-07-27 18:17:54 UTC
Created attachment 107445 [details] [review]
Bug 26072: Add ability to *not* force holds to be placed via the REST API even if AllowHoldPolicyOverride is enabled

There are use cases where we need to be able to place holds via the API, but not place holds that are in violation of the current holds policy. If AllowHoldPolicyOverride is enabled, holds placed via the API will succeed regardless of violations of the current hold rules.

Test Plan:
1) prove t/db_dependent/api/v1/holds.t