We (customers) do not know what is on the plan with Crowd, but this feature deserves to be included in some future releases of Crowd.

Thanks

+1. Would be very helpful.

+ Vote!

Or, alternatively, cloning of existing groups with all their existing configuration and ability to edit name/config during cloning process should also help. Appreciate, if you could prfioritize this!

+ Vote!

Or, alternatively, cloning of existing groups with all their existing configuration and ability to edit name/config during cloning process should also help. Appreciate, if you could prfioritize this!

++ vote ++ vote +++ vote for being able to rename groups after creation. pls move this up in priority in due time. thank you for your support.

Would be a most welcome addition. Deleting and recreating a group to change the name, for a group with a lot of users, is just not doable and sooooo 1980-ish..... Not being able to rename just blows my mind. 

++ vote, Atlassian should release this feature since this issue sit more than 5 years now.

It sounds like the group name is a primary key in the DB (I have not looked at the architecture, but just guessing since this hasn't been implemented).  If the group were some random ID and the name a field, then it could easily be changed.  In addition, it would give the ability to have multiple aliases to a group.

I find that we need to rename groups, but for the short term, would like to keep the old name until we have updated all the items referring to the group.  Having an alias or multiple names would allow that.

I'd like to strongly advocate for this suggestion.  The administrators of Crowd within my organization are not going to grant me SQL level access to their database.

I feel like we either need to support the renaming of groups, even if we had to do some manual work to update where they're being used, or we need to support the ability to clone existing groups.

But if you don't offer either, then there is no workaround for organizations in which access to relational databases is rightfully restricted.

A decade and this is still open. I guess nobody at Atlassian was ever doing a reorganization. Lucky guys!