-
Suggestion
-
Resolution: Unresolved
-
None
-
110
-
39
-
NOTE: This suggestion is for Confluence Data Center. Using Confluence Cloud? See the corresponding suggestion.
Hi everyone,
This is Kathleen from the Confluence team. Thank you for your interest in this suggestion.
We're considering this suggestion as a potential addition to our longer-term roadmap. We intend to review this request in about 12 months time, at which point we'll provide any relevant updates.
For the near future we've decided to prioritise other areas of Confluence Data Center.
You can read more about how we prioritise what to implement here.
To learn more about our recent investments in Confluence Data Center, please check our public roadmap and our dashboards containing recently resolved issues, and current work and future plans.
Kind regards,
Confluence Data Center
Add a possibility to change groupnames in Confluence
Workaround:
How to rename a group and preserve its permissions - Atlassian Documentation
Thanks for your interest in this issue.
This suggestion falls under a larger topic around user and group management which we are currently evaluating a number of popular suggestions. We will provide a further update in a few months time.
If you could help us understand how you intent to use this would be great.. e.g. only local groups, supporting renamed groups in LDAP, updating groups in LDAP, etc?
Cheers,
Adam Barnes - Confluence Product Management
- incorporates
-
- Closed
- is duplicated by
-
- Closed
- is incorporated by
-
- Closed
- is related to
-
CWD-4763 Inability for Crowd to detect renamed LDAP groups as Crowd does not track using its LDAP IDs yet
-
- Closed
-
- relates to
-
- Closed
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
[CONFSERVER-9159] Enable changing groupnames
This function is absolutely essential!
The fact that renaming groups is not possible regularly leads to a lot of problems and effort for us, including SQL renamings....
The request is now almost 17 years old and nothing has happened.
Hi everyone,
This is Kathleen from the Confluence team. Thank you for your interest in this suggestion.
We're considering this suggestion as a potential addition to our longer-term roadmap. We intend to review this request in about 12 months time, at which point we'll provide any relevant updates.
For the near future we've decided to prioritise other areas of Confluence Data Center.
You can read more about how we prioritise what to implement here.
To learn more about our recent investments in Confluence Data Center, please check our public roadmap and our dashboards containing recently resolved issues, and current work and future plans.
Kind regards,
Confluence Data Center
Is it a joke that we cannot rename groups in CONFLUENCE ? And a funnier joke that this ticket requesting a BASIC feature is "under consideration" since 2007 ??! 16 years and this must have feature is not yet implemented ? ARE YOU KIDDING, ATLASSIAN ? REALLY ?? Considering the prices of your products, this is really, really not serious... COME ON !
This is not working in the Confluence Cloud either. Come on Atlassian!
I really agree with Ricky Wang who said:
"Like many other here, renaming AD groups due to organizational restructuring happens and I happen to be going through it now and unfortunately landed on this thread.... It is quite an impactful design flaw that I'm surprised is still collecting dust..."
We change organizational names all the time and it is an administrative nightmare to delete groups and add them again to satisfy confluence. This is not a good solution since we use the AD groups on many fileshares too. And since confluence cloud not supports nested groups either this is making everything very difficult!
Agree with comments. Basic web development best practices demand a unique id that is immune to display name changes.
We're utilizing groups to handle teams access...a team changes a name and then this group is obsolete (the name)...this isn't acceptable (also the fact that were using the groups to show the members and now were stuck with the old name (with User List macro...that doesn't even allow to hide the name )... 
Like in SharePoint or other web applications the AD groups should be unique by their ID and not by the display name or group name. In SharePoint it is not needed to change any permission when an AD group changed the name.
Guys. This is pretty nuts.
Like many other here, renaming AD groups due to organizational restructuring happens and I happen to be going through it now and unfortunately landed on this thread.... It is quite an impactful design flaw that I'm surprised is still collecting dust...
a3e3471153f4 The workaround is linked above, in the description (https://confluence.atlassian.com/confkb/how-to-rename-a-group-and-preserve-its-permissions-948228977.html)
This function is absolutely essential, too!
The request is now almost 17 years old and nothing has happened. It`s unbelievable.