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

Improve the error handling with Org-level G Suite integration

    • 88
    • Hide

      Here is a new error message

      Heading: We're unable to update email account *
      This <<account_email_address> already has an Atlassian account. You can only update to an email address that doesn't have an Atlassian account.

      Show
      Here is a new error message Heading: We're unable to update email account * This <<account_email_address> already has an Atlassian account. You can only update to an email address that doesn't have an Atlassian account.
    • 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

      Some sync error between G Suite and Atlassian is not clear to the admins such as

      In that scenario specifically, the issue was that G Suite was trying to push an email update to an account, however, the target email address was already in use by a different Atlassian Account. That gives no clue to the admin what is happening and how they can resolve the issue.

      Suggested Solutions

      Improve how we handle the error messages in the new G Suite sync. In example:

      We can proceed and update <account_email_address> to <target_email> because <account_profile_link> is already using that email.

      Note: this does difficulty does not affect the sync of other accounts & groups

      I created an error message for this:
      *We're unable to update email account *
      This <<account_email_address> already has an Atlassian account. You can only update to an email address that doesn't have an Atlassian account.

            [ACCESS-962] Improve the error handling with Org-level G Suite integration

            David added a comment -

            While there is an issue with the actual error not being clear within the logs, I believe it's more impactful that such an error breaks the scheduled sync and does not notify admins that any future syncs will not run as this could cause compliance issues with the expectation that accounts are being controlled.

            David added a comment - While there is an issue with the actual error not being clear within the logs, I believe it's more impactful that such an error breaks the scheduled sync and does not notify admins that any future syncs will not run as this could cause compliance issues with the expectation that accounts are being controlled.

              d056dd6d7b90 Holly Makris (Inactive)
              jnunes@atlassian.com João Nunes
              Votes:
              12 Vote for this issue
              Watchers:
              31 Start watching this issue

                Created:
                Updated: