This issues is fixed as part of new Atlassian cloud - G Suite integration. Please raise this ticket if you are still facing this issue.

This can be a higher-impact issue for customers than it sounds like you appreciate. Here's what we just experienced:

• the person who happens to have originally configured the Atlassian / Google integration leaves the company, and their account is disabled.
• nobody else, administrators included, can now log in to Atlassian
• this means that nobody can follow the workaround to delete/re-add the google integration under a different account

Furthermore, while you say this is a limitation of using OAuth with Google, that is empirically not true: we use a number of hosted tools that authenticate with Google accounts, and this is the only one that failed when the user in question had their account disabled. Surely there's a way of implementing Google OAuth without tying it to one specific user's individual account?

(Incidentally, we were able to resolve this by re-enabling the account in question for long enough for another admin to log into Atlassian and change the Google integration. But this seems unlikely to be viable in general.)

I have reworded this as a bug rather than a suggestion. Note, however, that this is not something we can reasonably fix on our side as it is a limitation of using OAuth under a user's account.

To avoid the problem we can look at making this more obvious in Cloud admin and calling it out in our documentation.