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

Improve how G Sync group management works: delete groups from sync without the need of deleting the integration

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

      Currently, there is no option to delete groups from the sync and make it a site group without removing the integration. We do have the option to delete the group from Org > Directory > User provisioning but that would also delete it from the site.

      It would be great to have the option to remove a group from the sync so the site/org admins can manage it the way they want. Then, if they need to re-sync that through Google, they can edit the settings and select that group again then resolve group conflict.

      Suggested Solutions

      Create a feature that allows org admins to remove synced groups from the integration without having to delete the integration nor delete it from the site. The idea is to keep that group and the users within it as a site group so they can manage it and add other users that are not part of the sync.

            [ACCESS-1418] Improve how G Sync group management works: delete groups from sync without the need of deleting the integration

            Atlassian Update - December 16, 2023

            Hi everyone,

            Thank you for bringing this suggestion to our attention.

            As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.

            Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it.

            While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.

            Thank you again for providing valuable feedback to our team!

            Matthew Hunter added a comment - Atlassian Update - December 16, 2023 Hi everyone, Thank you for bringing this suggestion to our attention. As explained in our new feature policy , there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order. Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it. While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket. Thank you again for providing valuable feedback to our team!

              maho Matthew Ho (Inactive)
              jnunes@atlassian.com João Nunes
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: