-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
211
-
5
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
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.
You can work around this in part given the queries at: https://confluence.atlassian.com/display/JIRAKB/How+to+identify+group+usage+in+JIRA
- is related to
-
- Gathering Interest
- relates to
-
- Gathering Interest
- mentioned in
-
Page Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JRASERVER-36740] Extend Group administration page to show more use locations
From my point of view, the "usage" list lacks a specific location when allowing groups in "Comment Visibility" restriction with global settings "Comment visibility => Groups & Project Roles"
Then a group can be used to restrict Comment visibility.
Pleae implement this feature which which will be time saving, My user cannot manage sprints using the JQL she has, and I need to know which projects she does not have access to,
Thank You
Groups are obviously stepchildren to the manufacturer.
- Insufficient information about group assignments
- No possibility to rename groups
At least showing project roles can not be such a big challenge
To know where a group is used is important since you may need to create a new group and move some users from the old group to the new group, and the new group members must still can access the projects that old groups joined.
A group can also be used in the "User Filtering" config of a "User picker" field. Can that be added to the list in the description please? And perhaps a SQL query to identify the groups could be added here?: https://confluence.atlassian.com/jirakb/how-to-identify-group-usage-in-jira-441221524.html
It would be great to have this in admin view, so I don`t have to check it via database
Voting for this issue because Jira Admins need to be able to see groups across Jira entities such as project roles in order to maintain security when using Crowd and Active Directory.
+1