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

      When the following conditions are met, a group conflict will trigger.

      • The provisioned group name matches an existing group with the same name on the target Atlassian site.
      • The existing group contains a different set of members compared to the members in the provisioned group. 

      When a conflict occurs, the admins need to resolve them manually via the org administration (see document). Admins can only resolve conflicts 20 at a time and this requires a lot of manual work when resolving a large number of conflicts (ie. 1000+).

      Suggestion : Ability to resolve group conflict at scale.

            [ACCESS-1445] Ability to resolve group conflict at scale

            And the GUI shows a lot of errors, so no only it needs a lot of clicks, one for 20, but you have to retry very often and it takes hours to resolve 500 groups. Please allow us to it with one click - we provision groups with members, and there is no reason why we should not be able to overwrite ORG groups with better data in large.

            Bruno Abele added a comment - And the GUI shows a lot of errors, so no only it needs a lot of clicks, one for 20, but you have to retry very often and it takes hours to resolve 500 groups. Please allow us to it with one click - we provision groups with members, and there is no reason why we should not be able to overwrite ORG groups with better data in large.

              tshank@atlassian.com Tyler Shank (Inactive)
              rmacalinao Ramon M
              Votes:
              6 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated: