Atlassian customers have not been able to rename groups in cloud for a while now. If there’s a spelling mistake, change of team name, or anything that requires a change in a group name, it could not be done. The only option was to create a new group, move all the users from the old group to the new group, move all their permissions to the new group, then delete the old group… Or, live with it…
We understand our customers frustration, and are sorry you’ve had to wait 19 years, 11 months and 18 days for ID-6677 to be addressed.
From late February 2023, we’re excited to release a beta version of our group rename feature to most customers (a note on this below) in cloud. You’ll be able to rename groups from the group details screen at admin.atlassian.com. Group name changes will also appear within the Atlassian Access audit logs.
There are some caveats for now around which groups can be renamed:
We don’t allow special groups to be renamed yet, such as site-admins.
Groups that are synced via an IdP (SCIM) cannot be renamed, yet.
Being a beta feature, you may experience some slowness when renaming groups or unexpected errors, we’re working to improve this.
There’s still work to be done to enable this for all customers and all groups.
For now, the group rename feature will only be available on the improved user management UI. And we’re still working on getting all our customers onto that UI.
The group rename feature is not available for groups that are used in some Jira features. If your group is used in one of these Jira features, we’ll help direct you to the location to remove this group, so you can continue with renaming it, if you choose.
More Jira features will be unblocked over the next 12 months and you can track that progress via ID-8092.
This feature has been made possible by a number of changes we've made in our cloud architecture over the last few years. It will not address the same group rename issue that still exists in server and data centre.
Some apps may still rely on hardcoded group names to work. Jira and Confluence developer communities have put out blog posts asking Developer Partners to move off GroupName as keys and use GroupIDs instead.
If you experience some problems with your apps after changing a group name that the app utilises, please change the group name back or reconfigure your app to use the new group name. As mentioned above, you can track group name changes from within the Atlassian Access audit logs.
We understand how frustrating this has been for you, and we’re sorry this has taken so long to deliver. It has been a long time coming and I’m ecstatic that we’ve been able to finally deliver group rename to most of you.
For those that are still waiting to be able to use this feature in cloud, we’re working hard to deliver it to you as soon as possible.
We've found that if a group is renamed, and that group name is used within a Jira Automation, the automation will not work. We're working to include automations within the group rename limitation check.
The ability to rename groups is now available for all customers on our cloud products.
Kieren
Product Manager
Atlassian
Sydney
10 accepted answers
44 comments