Hi ea8de7b38038 

Any idea how close we are with this feature?  Its good we can log tickets to update the names but painful when you have over 20 groups that need to be updated

Chris

This is an awesome feature and wonderful news ea8de7b38038!

Great news to see there is finally traction with this feature. Hopefully its close to being rolled out without support intervention

Update: 21 May 2025

Dear Customers,

Thank you for your patience as our developers work hard to deliver this feature. I’m pleased to announce that our Support team now has the internal resources to rename SCIM groups on your behalf. This serves as a temporary workaround until the feature is fully implemented.

If you need groups to be renamed, please contact us at https://support.atlassian.com/contact/ with the current group names and their desired new names. We’ll be happy to assist you with these changes.

Please note, we can apply SCIM group renames for any Organization on the Centralized UI or any single site Organization on the Original UI. Unfortunately we can't apply it to multi-site Original UI Organizations. You can identify your UI here. 

This relates to a fidning on our side, that a rename from AZURE does not reflect to Atlassian. This alone requires us to be able to rename the groups in Atlassian at any given time. It sems the underlying ID (not label) is unchanged so renaming should be fine.

Consider:

1. Indicating in the groups management pages that a group is not of the same name as in IdP - it is valuable info
2. Optional: Allow to say: Keep in sync with IdP

That reminds me that it would be very useful to HIDE certain groups as we do not want people to use some. We can use rename feature to obscure them with ZZZ_NOT_USE_<group name> if THIS ticket is being addressed, but is see no silver lining here yet for IDP groups. 

Deletion and re-create would spoil any permissions where groups are used and.....to get groups-usage....again a feature that does not exist!

Sooooooooooo... How's it coming along???

Is Atlassian still "On Track" to have this ready this year?

Thank you for all of your feedback.

The ability to rename groups will be part of our SCIM platform rearchitecture project. Delivery of that project will be completed in various milestones currently scheduled throughout late 2025 and 2026.

We recognize that this timeline is not reasonable given the high friction associated with group rename, so we will also be providing a short-term solution. This short-term solution will be to provide APIs to assist with group rename.

We expect to launch these APIs in CY25 H1 and will be working to deliver them as quickly as possible. We will provide more details here as we have them. Thank you again!

Almost 5 years and still "Under Consideration". Can we an update from someone from Atlassian on this thread to see if we have any hope on getting this fixed?

All these easily solved problems are constantly waiting under 4, 5 or even 10 year tickets. 

Instead of creating new absurd applications (stop milking customers), you should first fulfil the demands of the customers!!

As I just heard from the support team, this request might be solved in FY25.

That would be great, as it is becoming more and more difficult to show in an audit (ISO27K / TISAX), that the correct groups from EntraID, actually have the correct permissions in the system.

https://support.atlassian.com/requests/CES-50765

LOL what are you talking about.  no its not. 
the ability to rename local groups was released like a year ago.  this is for IDP sync'd groups.
4 years of waiting still.

we need it for group synced groups from an external directory !

(deleted)

This is much needed for painfully obvious reasons

It always surprises me when I google what feels like a pretty standard task, in this case 'changing the name of a group', and find that it's a years-old suggestion ticket! 

There is a corresponding issue - open since 2007 !

https://jira.atlassian.com/browse/CONFSERVER-9159

some problems of customers simply seems to be ignored by Atlassian.

This is a big problem in our company because we need to create a new group then replace the group in Permissions scheme and many other config.

Same here. We urgently need solution for sync from azure ad to Atlassian cloud. Thank you

i need the group display name to be synced from azure ad to Jira cloud. 

With every restructure in our company i need to create new groups... which is ridiculous

Welcome to the future of agile cloud ci/cd.

this feature is definitely needed!
it cause many problems, that group rename is not possible.

It seems, that the key for a group is the name of a group, not an identifier.

But a name of a group can change

feature request is now older than 4 years! and nothing has happened.

The basic renaming feature took 20 years to be implemented so I assume that somewhere in my children's generation this SUPER ADVANCED feature will be implemented too.

PS>I know a good lawyer who can include this in our wills to pass it on as a task.

Definitely need this feature! 

A very much needed and required functionlity so definitely in SUPPORT of this.

This is also affecting my organization. Though it's not a critical issue, it's just bizarre that the name on Atlassian Cloud cannot be updated, even manually by supporters, when the group's name is updated in Workspace.

The group continues to sync from Workspace to Atlassian without issue, so clearly the name difference is not an impediment to syncing.

And in fact, in the "Select users to sync" option within "Identity providers" in "Atlassian Administration," under the "Sync users only in specific groups" option, we do see the updated names for the Workspace groups - so it's clear Atlassian can obtain the updated name, as well.

This is an absolute necessity if you are going to advertise as an enterprise-level application.

I am floored by how much Atlassian is charging, when basic features like this are not supported.

Atlassian Support, what is the standing of this 3 year old request?  t
The 20 year old request to rename groups is being worked on, why is this not given any attention.  

This is such a shame for the level of the product you are selling.
Cannot believe that such a basic tasks requirement is still under consideration after so many people have expressed their desire and need of it.
@Rodrigo B.- what are you currently working on!?

Can this please be implemented? We're having issues with a mess of group names because of this inability to rename these groups

It would be a lot easier to transition to Access provisioning if it could take over existing local groups, then allow for renaming of groups within Azure.

we definitely need a support for changing groups' name through the SCIM.

Having to rebuild groups, then  add the group to all permissions and boards makes this un-useable.  what a terrible design. exactly everything I've come to expect from Atlassian.

It was obviously rushed.  Their cloud products lack feature parity with the on-prem versions they replaced.

+1 PCS-175323

Questionable that this is listed as a suggestion.
Facilitating the renaming of a user/group you'd think would be bread and butter of a directory service.

If Atlassian Cloud want's to be taken seriously as an enterprise grade platform then this really should be classified as a bug.  Either the development of this was rushed or it was poorly scoped initially.

Same, this is impacting my organization negatively with Azure AD.

Can confirm, this would be exceptionally useful for us as well.

We're having the same issue. 

Agreed Justin !  As for #3 (investigating permission use) I've been using Bob Swift/Appfire's CLI (Jira Command Line Interface) app. It has been a life saver for Jira and Confluence user/group management. (Paid app, unfortunately, but SO worth it.)

You can dump a csv list of where the group(s) are used and then run a CSV to add/remove the groups where needed. It's saved me SO much time.

Let's hope they get this one going soon!

Mark

It's completely crazy that this isn't a feature. As others have mentioned, re-orgs take places frequently in growing companies and the inability to sync IdP group names increases the administrative overhead by at least 10x. I have to:

1. Create a new IdP group
2. Create a new Atlassian group
3. Investigate all of permissions that the old Atlassian group was granted (Jira projects, Confluence pages, product access, etc) which is itself a monumental task
4. Make all of the necessary changes to the new group
5. Delete the old Atlassian group
6. Delete the old IdP group

Instead of the way that it works with just about every other app out there:

1. Rename IdP group, Atlassian group name is automatically updated
2. Job done, grab a coffee

The same feature is needed to Azure AD sync too !

At least a workaround.

We need that feature too! Should not be a reactor technology.

Sorry, my answer may be not satisfying. We are migrating to another vendor and product.

Hello 2fddf8e388f8, would you share your solution with us?

@ Ralf that's still needed nonetheless!

No need any more, we have found a different solution.

I'm just flabbergasted that this does not work. Unbelievable. Seriously Atlassian?

We badly need this feature too!! 

Hi everyone,

I am the Product Lead for Atlassian Access, and wanted to point out that we are working on delivering ID-6677, which is the foundation to enable us to work on this feature request itself.

Thank you for your patience and feedback!

RODRIGO BECKER
Product Lead, Atlassian Access

Alin, yes others really want this feature, it's not only you!

Mike, as unbelievable as it may sound, I think you are spot on with your hunch that they have references by group name. Every time I have talked to Atlassian about this, the response is that it is a major change to implement, and they will look at it somewhere down the road as part of a permissions overhaul.

It's almost as if Atlassian has built their products to reference groups by name instead of some internal unique identifier and therefore they don't have a good way to rename groups.

Wow, these amazing support people from Atlassian are closing my request to have this issue resolved with a comment that I should keep an eye open here. Their answer is that this topic is not hot enough and it has not drawn enough attention to be taken into consideration.

Isn't there anyone else who needs this feature? Or even if you do not need it now, can you see the importance of such a basic feature in the future? Please share this with others and make this burn

Bump - seems like a feature that should be included. Teams typically change naming conventions for groups as time passes and this feature is a no-brainer.

Having to create a new group with the desired name, and deleting the old group is a ridiculous workaround. As a Jira admin of a small organisation, this ends up being a lot of work - needing to update 40 or so projects needs patience and care. How much pain do larger organisations with hundreds of projects go through?

For the price we pay for Access, you would think that group renames would have been made possible whilst the product was still in Beta! 

Is there an ETA on this feature? We also have AD groups with departments as the names. Reorganization or mistakes are found and it is very cumbersome to have to re-do group access across all the projects. Thanks.

Guys, 30 months have passed since this incompatibility was first presented. Have you done nothing in this regard?

LE:

Hello,

We are in great need of this functionality.
I imagine that not only us, but every other business is build on groups and accesses related to those groups and since this renaming feature does not work, I see it as a direct limitation for further growth and evolution of our company. At the moment we would like to expand and to bring new naming conventions and security features that would support our continuous evolution but we are faced with the requirement to create new groups and redo all permissions instead of just using a basic renaming feature.

Please excuse my honesty, but I can only see it that Atlassian is our number one enemy when it comes to the future development of our business.

The number of hours and other resources needed to invest in such a recreation of groups just does not fit in our plan and if we are forced to do so, then I would focus this huge amount of resources in migrating to a new service provider. This way we will not be faced with the same issues in the future.

In other words, if you force us to do a change, then we change you.

The person who reported this issue 30 months ago, have already told you bye bye!

Regards,