Uploaded image for project: 'Atlassian Access'
  1. Atlassian Access
  2. ACCESS-994

Improve Org-level Gsync/G Suite error message handling

    XMLWordPrintable

Details

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

    Description

      Problem Definition

      When the integration tries to update and synced account email address to a different one that is already tied to an Atlassian account, the process fails and displays an unspecific error in the screen as we can see below:

      Only the support team has access to the logs that shows the cause for that error, therefore, the admins have no way to know how they can work around this situation without opening a ticket.

      Note: despite the error message the sync does not stop because of this difficulty. It will be triggered every 4 hours to add/remove/change other users but that update will still fail.

      Workaround:

      • Org Admins: Solution for the error when you know what update was pushed
      1. Access the target email account at the org (Org > Directory > Managed accounts > select the user)
      2. Change that account's email address to a different prefix i.e. prefix.old@yourdomain.com
      3. Trigger a manual sync at Org > Directory > G Suite that will allow the integration to update the account.
      • Org admins: solution for the error when you don't know what is the update being pushed
      1. Open a support ticket. When you know the accounts involved in this issue, proceed with the changes mentioned above.

      Suggested solutions:

      Create a better error message that specifies to the org admins what changes are failing so they can proceed with the changes without the need of creating a support ticket.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              jnunes@atlassian.com João Nunes
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: