-
Suggestion
-
Resolution: Unresolved
-
379
-
-
Problem Definition
Ability to rename groups after they've synced to the organization from an identity provider.
Suggested Solution
The customer wants to rename groups after they've synced to the organization from an identity provider.
Org audit log should also reflect this changes for monitoring large scale changes.
Why this is important
The customer wants the renamed groups to appear in the organization from an identity provider.
Workarounds
- Use the synced group and just know that it will have the old name in Atlassian Cloud. Group memberships will remain up to date.
- Create a new group with the new name in your identity provider and sync that new group.
- Delete the group in Atlassian Cloud, then sync the group again from your identity provider.
- duplicates
-
- Closed
- is blocked by
-
- In Progress
- is related to
-
- Gathering Interest
- relates to
-
- Closed
-
ACE-5981 You do not have permission to view this issue
-
CES-61688 Loading...
-
- blocks
-
- mentioned in
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
[ACCESS-800] Ability to rename groups after they've synced to the organization from an identity provider.
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.
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.
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.
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!