• 321
    • 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 – 13 March 2023

      Hey everyone,

      We are happy to announce that the rollout of group rename feature has been finished to 100% of all organizations on the new administration experience, hence, after 20 years and cake 9 days, we will finally close this feature request for cloud.

      A good reminder that there are still dependencies in Jira to make group rename perfect, and those are tracked in detail on Group Rename dependencies tracking (ID-8092).

      For those customers still on the legacy administration experience, we are committed to unblock you, all dependencies for migration into the new experience should be addressed throughout 2023, current end date on December, as a dependency is unblocked and shipped to production, we will already migrate the organizations that were unblocked. Please, feel free to ask your questions or concerns on this ticket, even after it is closed, I will commit to answer any questions for the time being on a best effort.

      Thank you, as always.

      RODRIGO BECKER
      Product Lead, Atlassian Access

      Atlassian Update – July 11 2024

      We are happy to announce that 100% of Cloud organizations, including those on the legacy administration experience, can now access the ability to rename groups.

      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
          1.jpg
          724 kB
        2. celebrating-12-plus-of-being-ignored.png
          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
          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
          screenshot-1.png
          16 kB
        9. screenshot-2.png
          screenshot-2.png
          3 kB

            [ID-6677] Renaming groups after creation.

            Hahaha no it's not Joseph,
            Here is our next battle : https://jira.atlassian.com/browse/ACCESS-800

            Charlie Laigle added a comment - Hahaha no it's not Joseph, Here is our next battle : https://jira.atlassian.com/browse/ACCESS-800

            Hello ! 

            Just a quick question regarding this feature 

            Does the renaming is also available when we rename a group from the active directory ? (Managed groups) 

            Thank you ! 

            Joseph HANI added a comment - Hello !  Just a quick question regarding this feature  Does the renaming is also available when we rename a group from the active directory ? (Managed groups)  Thank you ! 

            Hi Team,

            we are not able to Edit still

             

            Thanks

            Shaik Ameenulla added a comment - Hi Team, we are not able to Edit still   Thanks

            Oh my god, it's finally here i'm crying

            Charlie Laigle added a comment - Oh my god, it's finally here i'm crying

            This is FINALLY available in our instance! 

            Navigate to Atlassian Administration > Directory > Groups > [Group]

            There is a new option under the ... (ellipsis) menu to Edit Group Name.

            If the group is associated with any Jira queries/items, you will get a notification that the group name cannot be changed.

            michelle.bachmann added a comment - This is FINALLY available in our instance!  Navigate to Atlassian Administration > Directory > Groups >  [Group] There is a new option under the  ...  (ellipsis) menu to  Edit Group Name . If the group is associated with any Jira queries/items, you will get a notification that the group name cannot be changed.

            Rodrigo B. added a comment -

            Hi f9b72c0781f5,

            That is strange, if you are seeing the interface from the second screenshot, you should have the feature. Please open a support request on support.atlassian.com so we can investigate further!

            Thanks

            RODRIGO BECKER
            Product Lead, Atlassian Access

            Rodrigo B. added a comment - Hi f9b72c0781f5 , That is strange, if you are seeing the interface from the second screenshot, you should have the feature. Please open a support request on support.atlassian.com so we can investigate further! Thanks RODRIGO BECKER Product Lead, Atlassian Access

            Rodrigo B. added a comment -

            Hey 198a0d57c156,

            We actually have this feature request ACCESS-800 that will be used in the future for group renames in SCIM, you can follow it for when we send an update once we start work on this feature, somehow I missed it earlier, sorry!

            Thanks!

            RODRIGO BECKER
            Product Lead, Atlassian Access

            Rodrigo B. added a comment - Hey 198a0d57c156 , We actually have this feature request ACCESS-800 that will be used in the future for group renames in SCIM, you can follow it for when we send an update once we start work on this feature, somehow I missed it earlier, sorry! Thanks! RODRIGO BECKER Product Lead, Atlassian Access

            Hi Rodrigo.

            If I compare the Groups screenshot from here https://community.atlassian.com/t5/Atlassian-Access-articles/User-management-for-cloud-admins-just-got-easier/ba-p/1576592?lightbox-message-images-1576592=125122i220A1DD8DC3FDBEF with our site, I see it's the same. Why could it be, then, that we don't have the option to rename groups?

            Alfonso Leiva added a comment - Hi Rodrigo. If I compare the Groups screenshot from here https://community.atlassian.com/t5/Atlassian-Access-articles/User-management-for-cloud-admins-just-got-easier/ba-p/1576592?lightbox-message-images-1576592=125122i220A1DD8DC3FDBEF with our site, I see it's the same. Why could it be, then, that we don't have the option to rename groups?

            9df4610e264f 

            How to request a migration ? Should I open a support ticket ?

            You can open a support ticket and our support team will work with you to give you options on how to move to the new UI.

            Eventually all customers will be moved to the new UI. When depends on the setup of the customer's org and admin roles.

            Kieren (Inactive) added a comment - 9df4610e264f   How to request a migration ? Should I open a support ticket ? You can open a support ticket and our support team will work with you to give you options on how to move to the new UI. Eventually all customers will be moved to the new UI. When depends on the setup of the customer's org and admin roles.

            Aileen added a comment -

            Thank you for the update Rodrigo. 

            Don't see groups under the directory so we must be on the legacy admin experience

            I was looking under user management> groups

            **Will this ticket be updated once EVERYONE is able to edit groups?

             

            Aileen added a comment - Thank you for the update Rodrigo.  Don't see groups under the directory so we must be on the legacy admin experience I was looking under user management> groups **Will this ticket be updated once EVERYONE is able to edit groups?  

              rbecker Rodrigo B.
              5820fc1290ae Alwyn Schoeman
              Votes:
              1810 Vote for this issue
              Watchers:
              842 Start watching this issue

                Created:
                Updated:
                Resolved: