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

Support Nested Groups in Atlassian Cloud platform

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Won't Do
    • None
    • 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

      "Enable Nested Group" is turned off in Atlassian Cloud platform. Atlassian Cloud customers would like to get this feature enabled as since Jira 4.3 release, the new user management has the ability to use nested groups.

      It seems that the reason behind disabling this is that: there is a potential risk that Atlassian Cloud licence will not work properly with nested groups.

      Suggested Solution

      Implement nested group feature as implemented in Jira Server.

      Workaround

      Nested groups flattening via Cloud IdP - nested groups aren’t supported in Atlassian Cloud, but you can keep the nested structure in your external user directory and use the flattened one in Cloud. A flattener keeps proper group memberships by automatically recreating memberships from your nested structure in the flat structure, and then adding users to all the required groups.

      Consider syncing groups via IdP that supports the feature - here’s a summary of how identity providers supported in Atlassian Cloud handle nested groups:

      https://support.atlassian.com/migration/docs/prepare-nested-groups-for-cloud-migration/ 

      For example, Azure AD supports nested groups:

      If you'd like to use flattened nested groups with AzureAD, please can check Early Access Program for Nested groups flattening between Atlassian cloud and Azure AD 

              Unassigned Unassigned
              adiallo Abdoulaye Kindy Diallo (Inactive)
              Votes:
              65 Vote for this issue
              Watchers:
              106 Start watching this issue

                Created:
                Updated:
                Resolved: