Enable any user to delete an epic
Problem to solve
The current state of deleting epics is that he user must have permission to delete an epic. If the user does not have permission, they do not see the Delete option within the UI, and can only close epics.
The issue here is that:
- The ability to delete epics is not discoverable
- Users may create extraneous epics and not be able to delete them. This causes either:
-
- Bloat of 'Closed' epics
-
- The user with delete permissions having to review epics and delete them for others
-
Proposal
-
Most risk: Allow any user to delete epics
- Any user across all a more flexible group permission can delete an epic with full understanding of the ramifications of that action
-
Less risk: Allow any user to see the ability to delete epics, but enable them only to request deletion instead of the deletion being immediate
- Any user of the group can request that an epic be deleted, which maybe prompts a modal or something else with the CTA being to request that the epic be deleted. It must still then be reviewed and actually deleted by someone with permission.
Questions and needs
- At what touchpoints do we allow epic deletion? At what touchpoints should we allow deletion?
- Who exactly has permission to delete epics?
- What would be the risk of allowing anyone to delete epics?
- Is there a way to successfully mitigate those risks (better friction, toasts, archiving and allowing to undo for xx days, etc)?
- If more users we able to delete, what would be the optimal permission level?
Edited by Alexis Ginsberg