Uploaded image for project: 'Identity'
  1. Identity
  2. ID-6677

Renaming groups after creation.



    • 300
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.


      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      Atlassian Update – 17 January 2023

      Hi everyone,

      Happy New Year! We hope you enjoyed your holiday time!

      First of all, thank you to everyone who signed up for the beta since last year month, unfortunately we had few eligible candidates, so we'd like to ask you again to volunteer for it, please use this form, guidance will be on it as well. It's important that we have a good sample of users before we start the full roll out of the feature.

      We will get in touch with the eligible candidates in the following days. If you haven't been contacted, it means that your organization was not eligible for the time, it's likely this was because it was not on the improved user management UI, and we won't be able to change that for now.

      We are at risk to keep our timeline for February, we could have a few weeks delay (product development life), but we will keep you posted as always. At this moment, what you can do to help is to volunteer for the beta, using the form above. Ask away any questions you might have on the comments of this ticket, and I will do my best to answer them!

      See you the third week of next month, or earlier if we have valuable news to share!

      Thank you, as always.

      Product Lead, Atlassian Access

      Atlassian Update – 20 December 2022

      Hello everyone,

      Thank you for your patience through all communications on this suggestion ticket. Great, Scott! I’m from Brazil, and, just realized that our customers in the Asia-Pacific area live in the future (GMT+ timezones), so I will start being more specific on dates to set the right expectations, as well!

      As per our last month’s communication, we made the conscious decision of launching the feature with limitations in December, and continue working on it to release each missing dependency. But as it turns out, we found an additional dependency and also a bug that had to be worked before launch, which did push things back another sprint, and with the holidays around the corner, we have to be honest with you folks, and set expectations again.

      Our timeline has been extended to January-February, where in end of January we will start the roll out for a smaller group of customers, and then do a full roll out in February. We will maintain the same cadency of updates to this ticket, on the 15th day of each month, Pacific Standard Timezone.

      Not done yet! We wanted to share these screenshots of the feature:

      As you can see, we will handle the dependencies on the UI, and provide you with shortcuts to sort them out if needed, and moving forward we will work out each dependency until everything is automagically done in the backend.

      The new feature will only be available for customers on the improved user management UI, which is a big parallel chunk of work ongoing to migrate all customers to it.

      If you’d like to be a part of the early rollout in January, please complete this form.

      We acknowledge that we are postponing this once again, which will cause frustration. In the most open and honest way possible to you; our customers, please keep on trusting us to deliver this most wanted feature.

      Thank you, as always.

      Product Lead, Atlassian Access

      Past Atlassian Update – 13 September 2022

      Hello everyone,

      We bring good news, this feature is under development by a dedicated team, and we are currently on track to get it ready by the end of the year, in December, 2022.

      We will maintain monthly updates to inform you the status of our progress (good or bad news), and in the spirit of our values, we want to be open with you. This has been a challenging problem to solve due to the complexity of the products themselves, and we wanted to find a solution that matches the future state of the administration experience for all of our Atlassian Cloud services. But we are happy and confident with the solution explored and chosen, hence we are coming back to you now.

      We sincerely thank you for your patience, and stay tuned for another update by October 14th,

      Product Lead, Atlassian Access

      Original request description:

      As a JIRA administrator I am responsible for managing a large installation with multiple users and groups. Given the dynamic nature of my environment it is very difficult for me to create the correct user group name which can be used for many projects later on. I need to be able to rename the user groups, to reflect the changes my organisation undergoes.


        1. 1.jpg
          724 kB
        2. celebrating-12-plus-of-being-ignored.png
          99 kB
        3. Group_AddForProjectsAndRoles.groovy
          3 kB
        4. GroupHelper.groovy
          10 kB
        5. image-2022-12-21-01-32-41-386.png
          319 kB
        6. JIRA group name changed.png
          JIRA group name changed.png
          147 kB
        7. JIRA-rename-groups.xlsx
          9 kB
        8. screenshot-1.png
          16 kB
        9. screenshot-2.png
          3 kB

        Issue Links



              rbecker Rodrigo B.
              5820fc1290ae Alwyn Schoeman
              1775 Vote for this issue
              822 Start watching this issue