Uploaded image for project: 'Atlassian Guard'
  1. Atlassian Guard
  2. ACCESS-800

Ability to rename groups after they've synced to the organization from an identity provider.

XMLWordPrintable

    • 422
    • Hide

      Update: 21 May 2025

      Dear Customers,

      Thank you for your patience as our developers work hard to deliver this feature. I’m pleased to announce that our Support team now has the internal resources to rename SCIM groups on your behalf. This serves as a temporary workaround until the feature is fully implemented.

      If you need groups to be renamed, please contact us at https://support.atlassian.com/contact/ with the current group names and their desired new names. We’ll be happy to assist you with these changes.

      Please note, we can apply SCIM group renames for any Organization on the Centralized UI or any single site Organization on the Original UI. Unfortunately we can't apply it to multi-site Original UI Organizations. You can identify your UI here. 

      Show
      Update: 21 May 2025 Dear Customers, Thank you for your patience as our developers work hard to deliver this feature. I’m pleased to announce that our Support team now has the internal resources to rename SCIM groups on your behalf. This serves as a temporary workaround until the feature is fully implemented. If you need groups to be renamed, please contact us at https://support.atlassian.com/contact/ with the current group names and their desired new names. We’ll be happy to assist you with these changes. Please note , we can apply SCIM group renames for any Organization on the Centralized UI  or any single site Organization on the Original UI . Unfortunately we can't apply it to multi-site Original UI Organizations. You can identify your UI here . 

    • 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.

      Problem Definition

      Ability to rename groups after they've synced to the organization from an identity provider.

      Suggested Solution

      The customer wants to rename groups after they've synced to the organization from an identity provider.
      Org audit log should also reflect this changes for monitoring large scale changes.

      Why this is important

      The customer wants the renamed groups to appear in the organization from an identity provider.

      Workarounds

      • Use the synced group and just know that it will have the old name in Atlassian Cloud. Group memberships will remain up to date.
      • Create a new group with the new name in your identity provider and sync that new group.
      • Delete the group in Atlassian Cloud, then sync the group again from your identity provider.

            [ACCESS-800] Ability to rename groups after they've synced to the organization from an identity provider.

            SET Analytics Bot made changes -
            Support reference count Original: 421 New: 422

            Chris Gerasimou added a comment -

            Great news to see there is finally traction with this feature. Hopefully its close to being rolled out without support intervention

            Chris Gerasimou added a comment - Great news to see there is finally traction with this feature. Hopefully its close to being rolled out without support intervention
            Kenneth De Coster made changes -
            Current Status Original: *Update: 20 May 2025*


            Dear Customers,


            Thank you for your patience as our developers work hard to deliver this feature. I’m pleased to announce that our Support team now has the internal resources to *rename* SCIM groups on your behalf. This serves as a temporary workaround until the feature is fully implemented.


            If you need groups to be renamed, please contact us at [https://support.atlassian.com/contact/] with the current group names and their desired new names. We’ll be happy to assist you with these changes.


            {*}Please note{*}, we can apply SCIM group renames for any Organization on the *Centralized UI* or any *single site* Organization on the {*}Original UI{*}. Unfortunately we can't apply it to multi-site Original UI Organizations. You can identify your UI [here|https://confluence.atlassian.com/cloudkb/identify-your-organisations-user-management-ui-experience-1402667018.html].              		New: *Update: 21 May 2025*

            Dear Customers,

            Thank you for your patience as our developers work hard to deliver this feature. I’m pleased to announce that our Support team now has the internal resources to *rename* SCIM groups on your behalf. This serves as a temporary workaround until the feature is fully implemented.

            If you need groups to be renamed, please contact us at [https://support.atlassian.com/contact/] with the current group names and their desired new names. We’ll be happy to assist you with these changes.

            {*}Please note{*}, we can apply SCIM group renames for any Organization on the *Centralized UI* or any *single site* Organization on the {*}Original UI{*}. Unfortunately we can't apply it to multi-site Original UI Organizations. You can identify your UI [here|https://confluence.atlassian.com/cloudkb/identify-your-organisations-user-management-ui-experience-1402667018.html]. 

            Kenneth De Coster added a comment - - edited

            Update: 21 May 2025

            Dear Customers,

            Thank you for your patience as our developers work hard to deliver this feature. I’m pleased to announce that our Support team now has the internal resources to rename SCIM groups on your behalf. This serves as a temporary workaround until the feature is fully implemented.

            If you need groups to be renamed, please contact us at https://support.atlassian.com/contact/ with the current group names and their desired new names. We’ll be happy to assist you with these changes.

            Please note, we can apply SCIM group renames for any Organization on the Centralized UI or any single site Organization on the Original UI. Unfortunately we can't apply it to multi-site Original UI Organizations. You can identify your UI here. 

            Kenneth De Coster added a comment - - edited Update: 21 May 2025 Dear Customers, Thank you for your patience as our developers work hard to deliver this feature. I’m pleased to announce that our Support team now has the internal resources to rename SCIM groups on your behalf. This serves as a temporary workaround until the feature is fully implemented. If you need groups to be renamed, please contact us at https://support.atlassian.com/contact/ with the current group names and their desired new names. We’ll be happy to assist you with these changes. Please note , we can apply SCIM group renames for any Organization on the Centralized UI  or any single site Organization on the Original UI . Unfortunately we can't apply it to multi-site Original UI Organizations. You can identify your UI here . 
            Kenneth De Coster made changes -
            Current Status Original: *6th November 2024*

            Thank you for all of your feedback.

            The ability to rename groups will be part of our SCIM platform rearchitecture project. Delivery of that project will be completed in various milestones currently scheduled throughout late 2025 and 2026.

            We recognize that this timeline is not reasonable given the high friction associated with group rename, so we will also be providing a short-term solution. This short-term solution will be to provide APIs to assist with group rename.

            We expect to launch these APIs in CY25 H1 and will be working to deliver them as quickly as possible. We will provide more details here as we have them. Thank you again!             		New: *Update: 20 May 2025*


            Dear Customers,


            Thank you for your patience as our developers work hard to deliver this feature. I’m pleased to announce that our Support team now has the internal resources to *rename* SCIM groups on your behalf. This serves as a temporary workaround until the feature is fully implemented.


            If you need groups to be renamed, please contact us at [https://support.atlassian.com/contact/] with the current group names and their desired new names. We’ll be happy to assist you with these changes.


            {*}Please note{*}, we can apply SCIM group renames for any Organization on the *Centralized UI* or any *single site* Organization on the {*}Original UI{*}. Unfortunately we can't apply it to multi-site Original UI Organizations. You can identify your UI [here|https://confluence.atlassian.com/cloudkb/identify-your-organisations-user-management-ui-experience-1402667018.html]. 
            SET Analytics Bot made changes -
            Support reference count Original: 418 New: 421
            SET Analytics Bot made changes -
            Support reference count Original: 417 New: 418
            SET Analytics Bot made changes -
            Support reference count Original: 416 New: 417
            SET Analytics Bot made changes -
            Support reference count Original: 415 New: 416

            Carsten Schäfer added a comment -

            This relates to a fidning on our side, that a rename from AZURE does not reflect to Atlassian. This alone requires us to be able to rename the groups in Atlassian at any given time. It sems the underlying ID (not label) is unchanged so renaming should be fine.

            Consider:

            1. Indicating in the groups management pages that a group is not of the same name as in IdP - it is valuable info
            2. Optional: Allow to say: Keep in sync with IdP

            That reminds me that it would be very useful to HIDE certain groups as we do not want people to use some. We can use rename feature to obscure them with ZZZ_NOT_USE_<group name> if THIS ticket is being addressed, but is see no silver lining here yet for IDP groups. 

            Deletion and re-create would spoil any permissions where groups are used and.....to get groups-usage....again a feature that does not exist!

            Carsten Schäfer added a comment - This relates to a fidning on our side, that a rename from AZURE does not reflect to Atlassian. This alone requires us to be able to rename the groups in Atlassian at any given time. It sems the underlying ID (not label) is unchanged so renaming should be fine. Consider: Indicating in the groups management pages that a group is not of the same name as in IdP - it is valuable info Optional: Allow to say: Keep in sync with IdP That reminds me that it would be very useful to HIDE certain groups as we do not want people to use some. We can use rename feature to obscure them with ZZZ_NOT_USE_<group name> if THIS ticket is being addressed, but is see no silver lining here yet for IDP groups.  Deletion and re-create would spoil any permissions where groups are used and.....to get groups-usage....again a feature that does not exist!

              d056dd6d7b90 Holly Makris (Inactive)
              rdey@atlassian.com Ratnarup (Inactive)
              Votes:
              574 Vote for this issue
              Watchers:
              419 Start watching this issue

                Created:
                Updated: