https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42264 Bug ID: 42264 Summary: Ungrouping holds or grouping existing holds requires top-line reserveforothers permission Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Hold requests Assignee: koha-bugs@lists.koha-community.org Reporter: sbrown@bywatersolutions.com QA Contact: testopia@bugs.koha-community.org CC: gmcharlt@gmail.com, lisette@bywatersolutions.com, tomascohen@gmail.com While staff with the place_holds permission (and no other permissions from reserveforothers) *can* create a hold group by selecting multiple bibs in search results and choosing the 'Treat as hold group' option on the 'Place holds' screen, they cannot create a hold group from existing 'standard' holds or ungroup a hold group. Grouping existing holds and ungrouping holds requires the top-line reserveforothers permission, but it should either be part of place_holds or be a separate permission so that staff needn't also have alter_hold_targets and modify_holds_priority in order to use hold groups. To replicate the error with creation: -Use a staff patron account with only the place_holds permission from the reserveforothers group -Create 2 or more standard holds for another patron -In the regular patron's account, select the standard holds and click 'Group holds' -On the modal, click 'Group' -Note the error message: "Authorization failure. Missing required permission(s)." To replicate the problem with ungrouping: -Find/create a patron with a group hold using a staff account with top-line reserveforothers permission -Sign in using a staff patron account with only the place_holds permission from reserveforothers -Go to the regular patron account where the group hold was placed -Click the number in the 'Hold group' column, then select 'Ungroup holds' from the modal -Note that the modal disappears with no error message, but the hold has not been ungrouped -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.