Issue Summary

When a group is deleted, and the group is used in a page's restriction, the restriction for this group is not listed on the space settings > restricted

The group is also not displayed in the page restrictions list, giving the admins/user the impression only exiting groups and users are added to the page restrictions.

When you check in the database, the group deleted in admin.atlassian.com, is still listed in the page restrictions.

This is an issue since if you as an admin, remove all restrictions in the space settings > restricted, there are no restrictions left to remove in the UI, but the page is still restricted to any user, since the group no longer exists and there is no option to remove it from the UI or APIs.

Checking directly on the page > restrictions, also does not list the group deleted there.

When the group is re-created with same name, the issue with the restriction still persists.

Steps to Reproduce

1. Create a test group, TestGroup.
2. Add TestGroup to the Space's Space permission.
3. Create a page in the Space.
4. Add view/edit restrictions to the page, and add yourself, and TestGroup and another existing group or user to the restrictions.
5. Go to space settings > Restricted, you should be able to see the group there
6. Now delete the TestGroup group.
7. Go back to the Go to space settings > Restricted and do a hard refresh, you should no longer be able to see the group listed there
8. Click on the padlock icons to remove all restrictions visible (view and edit)
9. Try to access the page just removed "all restrictions"
10. Recreate a new user group with the same name, TestGroup.
    • Add your user into the group.
11. Try to access the page

Expected Results

1. Group should be removed from restrictions when it is deleted, or at least displayed in the page restrictions to be removed

Actual Results

1. Deleting a group causes the page restriction to be restricted, even though the groups were not showing in the restrictions UI to be removed.
2. Re-creating a group with the same name gives access to users in that group

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available