Problem Definition

When a group is deleted on a Cloud site and the group is used in permissions configurations on Jira or Confluence, then the group is removed from the permissions configuration.

This can have catastrophic effects on product access or data access at the product level, i.e. end users can no longer access their data. Re-creating a new group with the same name as the deleted group doesn't help resolve the problem because the new group would have a new groupId and the permission configuration record is orphaned/corrupted.

Suggested Solution

• Block deletion of groups where the groups are used in Jira/Confluence permissions configurations
• Show the org. admin a message showing where the group has been referenced in the permissions configuration page(s) and have a message warning the org. admin regarding loss of access to product or data

Why this is important

• The restoration process to recover lost permissions configurations can take days to complete and the effects for end users are often very disruptive to normal operations

Workaround

No known workarounds, if a workaround is found - the workaround will be added here.