-
Suggestion
-
Resolution: Unresolved
-
None
-
88
-
-
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.
- is detailed by
-
ACCESS-961 Improve error messaging on G Suite configuration page
- Closed
- relates to
-
ID-7646 Org-level Gsync/G Suite showing error message after failing in update a user's email address.
-
- Closed
-
-
ACCESS-994 Improve Org-level Gsync/G Suite error message handling
- Closed
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
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.