-
Suggestion
-
Resolution: Unresolved
Hi everyone,
We've launched the feature to rename groups in Atlassian Cloud, as per ID-6677.
As we informed in the above suggestion ticket, we decided to launch the feature in its earlier stages, as we know it can already benefit many of our customers, and, continue to work on the remaining dependencies, prioritizing the most impactful to the least, based on our usability analytics research.
On this ticket, we will track each dependency, to give you full visibility of what the work looks like, and what we are doing. The purpose of this ticket is not to gather impact, or prioritize work, the group rename feature is already a priority for Atlassian, and critical part of our roadmap.
Id | Depedency | Status |
---|---|---|
1 | Product Access | Done |
2 | Global permission | Done |
3 | Advanced Roadmaps - Plugin Permissions | Done |
4 | Project Roles | Done |
5 | Notification | Done |
6 | Issue Securities Scheme | Done |
7 | Share Permission | Done |
8 | JQL Filters - Subscription | Done |
9 | Permissions Scheme | Done |
10 | Advanced Roadmaps - Plan | Done |
11 | Workflows | Done |
12 | Announcements | Deprecated |
13 | Issue Comments | Done |
14 | User Picker Filter | Done |
15 | Board Administrators | Done |
16 | Worklogs | Done |
17 | Group Pickers - Custom Fields | Done |
18 | JSM Assets | Scheduled |
19 | JSM Approvals - Group Pickers | Scheduled |
20 | Automation platform experiences | Done |
JQL Filter - Results are out of scope due to complexity in being a string that would need to change per JQL in the database, meanwhile, we know it's difficult to identify the blocking JQL, please use the workaround available in ID-8534.
Looking for user provisioning via SCIM group rename? Once all dependencies are fixed, we should start work on ACCESS-800.
Thank you!
RODRIGO BECKER
Product Lead, Atlassian Access
- blocks
-
ACCESS-800 Ability to rename groups after they've synced to the organization from an identity provider.
- In Progress
- has a derivative of
-
JSDCLOUD-14212 Trying to change group name fails due to CMDB - Assets usage
- In Progress
- is related to
-
JRACLOUD-83598 Announcements dependency for Group rename
-
- Closed
-
-
AX-91 It's not possible to identify which "JQL Filters - Result" a group is used in without support assistance when renaming group
- Gathering Interest
-
CONFCLOUD-80746 Reflect group name changes to the setting of Restricted Pages
- Gathering Interest
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
[AX-159] Group Rename dependencies tracking
All comments
Hi
Thanks for the rename of groups but having some sync issues with Jira global permission schema
Found out on Jira Cloud Global permissions its not updating the group names when renamed on Atlassian
Possible this is just a matter of time for sync to happen, im not sure please guide on this
Not great when this changes could affect a lot of users if not synced
When i looked at the links to find the group on the Atlassian i could see groupid="Name on the group"
https://xxx.atlassian.net/secure/admin/user/UserBrowser.jspa?group=administrators
Would suggest that the groups get changed to GroupID"ID number of the group" so its not depending on the group name
This would maybe also solve the group name lookup
But now im afraid that i messed something up by changing some group names thats not great