| Summary: | Deleting item should not automatically delete group | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Andrew Fuerste-Henry <andrew> |
| Component: | Cataloging | Assignee: | Bugs List <koha-bugs> |
| Status: | NEW --- | QA Contact: | Testopia <testopia> |
| Severity: | enhancement | ||
| Priority: | P5 - low | CC: | kyle, m.de.rooy, martin.renvoize, mnero |
| Version: | Main | ||
| Hardware: | All | ||
| OS: | All | ||
| GIT URL: | Initiative type: | --- | |
| Sponsorship status: | --- | Crowdfunding goal: | 0 |
| Patch complexity: | --- | Documentation contact: | |
| Documentation submission: | Text to go in the release notes: | ||
| Version(s) released in: | Circulation function: | ||
| Bug Depends on: | 24857 | ||
| Bug Blocks: | |||
|
Description
Andrew Fuerste-Henry
2020-08-21 15:15:43 UTC
That functionality was actually a specific request from the sponsor. If we want to change it, we'll need to use a syspref. I think deleting the volume with the last item makes sense, but maybe I am missing a use case here? If there is a hold on the item group that gets automatically deleted, the hold reverts to "next available item," which is not what a patron would want. Also, moving the last item in one item group to a different one, leaves behind an empty item group without deleting it. I would prefer this be a system preference with the option to batch delete empty item groups rather than have some automatically delete and some get left behind, although that might be a separate bug. |