-
Suggestion
-
Resolution: Unresolved
-
1,317
-
163
-
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Hi everyone,
Thank you for taking the time to share your challenges around identifying where groups are utilised within Jira. After a thorough review by the team, we have decided that we will not be able to implement this suggestion in the next 12-18 months. We will be maintaining this ticket's status as "Gathering Interest" in order to continue learning from all of you about pain points and challenges relating to this suggestion, and will continue to re-visit this ticket in our ongoing product planning.
We understand that this is not the update you may have been hoping for, especially given the longstanding nature of this issue. Please don't hesitate to contact me if you have any questions or feedback.
Regards,
Aditi Dalal
adalal@atlassian.com
Product Manager, Jira Cloud
Currently we only show when a group is used in:
- Permission Schemes
- Notification Schemes
- Issue Security Schemes
- Shared filters
A more complete list of locations where a group can be used is:
- Permission Schemes
- Notification Schemes
- Issue Security Schemes
- Shared filters
- Project Roles
- Global Permissions
- Custom field values
- Post functions in workflows
- Conditions in workflows
- Shared dashboards
- Filter subscriptions
- Plugins (we can't help check this one, because we don't know how plugins will use this)
We should extend this functionality to check as many places as possible because understanding the impact of changes to groups is very difficult for admins at this time.
Workaround
Permissions schemes
https://confluence.atlassian.com/jirakb/how-to-find-group-usage-in-permission-schemes-for-jira-cloud-via-rest-api-and-python-1217306462.html
Filters
A user with the Administer Jira Global permission can go to
YOUR_SITE_NAME.atlassian.net/rest/api/3/filter/search?expand=jql&overrideSharePermissions=true
and search for the group name to see which filter it is used in.
Once you know the filter's name you can go to
YOUR_SITE_NAME.atlassian.net/secure/admin/filters/ViewSharedFilters.jspa and make yourself its owner or delete the filter:
- incorporates
-
JRACLOUD-71967 Group usage - List of project permission per group
- Gathering Interest
- is duplicated by
-
JRACLOUD-77635 Report containing Group association with roles and projects
- Closed
- is related to
-
JRASERVER-36740 Extend Group administration page to show more use locations
- Gathering Interest
- relates to
-
JRACLOUD-77635 Report containing Group association with roles and projects
- Closed
-
ID-8534 It's not possible to identify which "JQL Filters - Result" a group is used in without support assistance when renaming group
- Gathering Interest
-
JRACLOUD-15907 collect and display usage statistics
- Gathering Interest
-
JRACLOUD-71967 Group usage - List of project permission per group
- Gathering Interest
-
JRACLOUD-75929 Improve User management reports
- Gathering Interest
-
JRACLOUD-78623 Provide report of permission schemes and associated users/groups
- Gathering Interest
Dear Atlassian team,
I kindly ask you to take this issue under consideration again. You have built a powerful, but also complex environment, in which managing of groups is a central aspect to create and keep control over rights, permissions and license usage across a multitude of products, projects, spaces and so on. In order to manage this, it is necessary to be able to manage groups, so creation, reordering, renaming and deletion of groups. Right now, deleting the wrong group can render whole spaces in Confluence unusable. (Page restriction on landing page of a confluence space set to that group, deletion of group leads to "ghost restriction" that cannot be removed by user or admin and hides the complete space with all pages from any kind of access, only solveable by cotnacting Support.)
Unless you identify and solve any issue regarding these permission management topics - which I assume isn't easy - giving your users and admins the option to at least see each and every usage of a user group is essential.
Regards
Michel Kangro