Separate Jira user email, from bitbucket

[Алекс]

Our team used their personal email to use our corporate Jira (cloud), they did this since we didn't have a corporate email.

Now we are using G-Suit and implementing "access management".

The first step was to ask our team to change their "Atlassian" ID from their personal to their new corporate accounts.

We encountered the following issue:

Some of the users got other Atlassian products on their current personal emails.

If they'll make the switch, it will mean that the will lose access to their personal repos in BitBucket & other altassian product. 

If we'll create a new user for them, that means we will lose their current ID (it's used in filters, comments, mentions, tasks, assignee, reporter ...etc.)

Any ideas or suggestions on how to solve this issue? 

Thanks.

[Theodora Boudale]

Hi @Алекс and welcome to the community!

Both Jira Cloud and Bitbucket Cloud use Atlassian accounts for authentication (the ones for https://id.atlassian.com/). This is to provide single login with the same account to multiple Atlassian Cloud products.

If a user has access to both products with the email myuser@example.com, then the Atlassian account with that email is used for authentication in both products. It is not possible to separate them because it is one Atlassian account.

Some of the users got other Atlassian products on their current personal emails.

If they'll make the switch, it will mean that the will lose access to their personal repos in BitBucket & other altassian product.

Changing an Atlassian account's email will not affect the permissions of the account in Bitbucket Cloud, and the user will continue to have access to any Bitbucket repos they could access before. However, such an email change has other consequences that you need to take into account:

• If a user leaves the company after some time and they forget the password of their account, they won't be able to log in to the account and change the email back to their personal email address.
  
  
• If you verify the domain of the company email addresses in order to have managed accounts, these accounts will be considered to be owned and managed by the company. The users will not be able to make an email change to the account at all (this will only be possible for an Org Admin to do).
  • If a user leaves the company and you deactivate their account, then the user won't be able to access that Bitbucket account and their personal repos.
  • If you delete their account, then any repos owned by the personal workspace of said account will be deleted as well.

The options you have are the two ones you mentioned, either create new users or, if the users agree, they can switch the email of their existing accounts; I would suggest making sure though that they are aware of the things I listed above.

If they switch the email of their current account to your company email, they can create a new Bitbucket account with their personal email afterwards, and transfer any personal repos to a new workspace administered by that new personal account. This way they'll have one work account and a personal one. Things to take into account for this scenario:

• In case their current Bitbucket account has access to repos/workspaces not owned by them, they can ask the admin of said repos/workspaces to remove the current user and send an invitation to the new account with their personal email.
• Any existing activity in the Bitbucket repos, like comments, pull requests, will still be tied to their current user.
• The repo URL will change if they transfer repos, they'll need to take that into account for any integration.
• User access needs to be set up again after a repo is transferred.

I would suggest discussing all these things with your team in order to decide what option is best for you.

If you or any other member of your team have any questions, please feel free to reach out.

Kind regards,
Theodora