The way we handle user/group deletion could be improved:
The Problem with the Old Process
Previously, if you tried to delete a user or group that had items assigned to them, Eramba would block the deletion with a warning. You would then need to manually find every reference and unassign them.
How the New Inheritance Feature Works
With the new feature, when you delete a user or group that still has assignments, Eramba will let you choose a replacement, either another user or another group to automatically inherit those assignments.
The inheritance applies to:
- Items where the user/group was assigned in a role field
- Views and reports created by user
- Notifications
When triggered, you’ll see a dropdown where you select the inheriting user or group.
Special Handling
We’ve also ensured the change covers:
-
Records in comments and attachments
-
Entries in the activity log
Notes
- If a user or group is not assigned anywhere, the inheritance logic will not apply.
- Groups must still be empty before deletion.
- Access control settings are not inherited.
Related:
- When a user is deleted we are apparently deleting their comments too, this should not happen.
ref: Bug - Deleting users also deletes comments