https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29877
Bug ID: 29877
Summary: MaxReserves should be enforced consistently between
staff interface and API
Change sponsored?: ---
Product: Koha
Version: master
Hardware: All
OS: All
Status: NEW
Severity: major
Priority: P5 - low
Component: Hold requests
Assignee: [email protected]
Reporter: [email protected]
QA Contact: [email protected]
CC: [email protected]
To test:
1 - set maxreserves to 1
2 - set all/all circ rule to unlimited holds allowed total, holds allowed
daily, and holds per record
3 - confirm you can place 1 hold for a patron via staff interface, but the
second is blocked
4 - confirm you can place 1 for a patron via API, but the second is blocked
5 - set maxreserves to 0
6 - confirm you can place any number of holds for the patron via the staff
interface
7 - confirm you can place 0 holds for your patron via the API
8 - set maxreserves to blank
9 - confirm you can place any number of holds for the patron
10 - confirm you can place 0 holds for your patron via the API
We should make the API treat zero and blank as un-set, as the staff interface
does.
--
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.
_______________________________________________
Koha-bugs mailing list
[email protected]
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
