https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36346
--- Comment #4 from Katrin Fischer ---
I think this would just fix one case of forced holds, but the problem is a
wider one. There are some bugs around this that could be interesting to have a
look at. Entry point is:
Bug 31169 -
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36346
--- Comment #3 from Thibaud Guillot ---
I was thinking that if we have the possibility of forcing a hold even if it is
not authorized in the rules, the hold should still be found if it exists in
certain cases (those I list in the
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36346
Nick Clemens changed:
What|Removed |Added
CC||n...@bywatersolutions.com
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36346
--- Comment #1 from Thibaud Guillot ---
Created attachment 163339
-->
https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=163339=edit
Bug 36346 : Prevent moving to the next object on 'not_allowed' rule
Test plan:
1)
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36346
Thibaud Guillot changed:
What|Removed |Added
Status|NEW |Needs Signoff
--
You
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36346
Thibaud Guillot changed:
What|Removed |Added
Assignee|koha-b...@lists.koha-commun