Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Workaround for renaming groups in Crowd using Scriptrunner

Given that it is not possible to rename groups, would it be possible to use ScriptRunner to create a new group and then transfer all properties associated from another group to the new one so that it would essentially be like a rename from the end user's perspective?

1 answer

0 votes

Hey Robert,

I think it depends on what "all properties" means in your environment. If you know that Groups are only used in Permission Schemes and Roles, then you'd likely be able to loop through all permission schemes and all roles and replace $oldGroupName with $newGroupName - unfortunately things often aren't that simple as groups in Jira are possibly used in many other places (workflow conditions/post functions, notification schemes, add-ons, filter/board perissions to name a few). Given you're using Crowd, you also likely have more than 1 application, so you then need to repeat the same for Confluence (space permissions, user list macros, restrictions), Bitbucket (permissions) etc etc.

While the applications store a users GUID (mapped through from Crowd > AD/LDAP/etc) and understand how to change any flow on impact from a rename, groups are only stored with the groups name as a string as the primary key and foreign key throughout.

Managing a large scale environment, this is a significant frustration as refactoring when we need to change group names is either not done as much as it should be due to the effort involved, or, manually change what we know and have to wait for users to say something is broken and fix up after.

Suggest voting on https://jira.atlassian.com/browse/CWD-1599 to get the support, however even if/when Crowd supports it, every other app that can use Crowd needs to support it as well.

CCM

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase

The benefits of using Jira in different departments

Jira is a great tool to use across different departments. Forget that paperwork – switch to Jira and get that tasks done smoothly. Marketing Jira allows for a complete digital transformation of you...

86 views 0 5
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you