-
Suggestion
-
Resolution: Fixed
Often users will change their email addresses and sometimes they create a new Atlassian account with the new email, rather than changing the email associated with their old Atlassian account. This causes problems because they can no longer access the Bitbucket content associated with their old login when using their new login, because the content belongs to separate Atlassian accounts. They can't just close their new account and change emails on the old one if they've created content (e.g. repos) in the new one already.
In these situations it would be useful to be able to merge their old account into their new account so they have access to all their content from one account, at which point they can close their old account.
[ACCESS-1364] Merge Atlassian Accounts
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
| Component/s | Original: Account - Merge [ 61596 ] | |
| Component/s | Original: Access - Account Management [ 58903 ] | |
| Component/s | New: User Sync - Managed Accounts [ 53198 ] | |
| External issue ID | Original: 17923 | |
| Key |
Original:
|
New:
|
| Priority | Original: Low [ 4 ] | |
| Project | Original: Bitbucket Cloud [ 20310 ] | New: Atlassian Access [ 18910 ] |
| Component/s | New: Account - Merge [ 61596 ] |
| Description |
Original:
Often users will change their email addresses and sometimes they create a new Atlassian account with the new email, rather than changing the email associated with their old Atlassian account. This causes problems because they can no longer access the Bitbucket content associated with their old login when using their new login, because they're separate Atlassian accounts. They can't just close their new account and change emails on the old one if they've created content (e.g. repos) in the new one already.
In these situations it would be useful to be able to merge their old account into their new account so they have access to all their content from one account, at which point they can close their old account. |
New:
Often users will change their email addresses and sometimes they create a new Atlassian account with the new email, rather than changing the email associated with their old Atlassian account. This causes problems because they can no longer access the Bitbucket content associated with their old login when using their new login, because the content belongs to separate Atlassian accounts. They can't just close their new account and change emails on the old one if they've created content (e.g. repos) in the new one already.
In these situations it would be useful to be able to merge their old account into their new account so they have access to all their content from one account, at which point they can close their old account. |
| Description |
Original:
Often users will change their email addresses and sometimes they create a new Atlassian account with the new email, rather than changing the email associated with their old Atlassian account. This causes problems because they can no longer access the Bitbucket content associated with their old login when using their new login, because they're separate Atlassian accounts. They can't just close their new account and change emails on the old one if they've created content (repos etc.) in the new one already.
In these situations it would be useful to be able to merge their old account into their new account so they have access to all their content from one account, at which point they can close their old account. |
New:
Often users will change their email addresses and sometimes they create a new Atlassian account with the new email, rather than changing the email associated with their old Atlassian account. This causes problems because they can no longer access the Bitbucket content associated with their old login when using their new login, because they're separate Atlassian accounts. They can't just close their new account and change emails on the old one if they've created content (e.g. repos) in the new one already.
In these situations it would be useful to be able to merge their old account into their new account so they have access to all their content from one account, at which point they can close their old account. |
Linked to Atlassian account suggestion ID-240 which applies to all products, not just Bitbucket.
| Description |
Original:
Often users will change their email addresses and sometimes they create a new Atlassian account with the new email, rather than changing the email associated with their old Atlassian account. This causes problems because they can no longer access the Bitbucket content associated with their old login when using their new login, because they're separate Atlassian accounts. They can't just close their new account and change emails on the old one because they've created content (repos etc.) in the new one already.
In these situations it would be useful to be able to merge their old account into their new account so they have access to all their content from one account, at which point they can close their old account. |
New:
Often users will change their email addresses and sometimes they create a new Atlassian account with the new email, rather than changing the email associated with their old Atlassian account. This causes problems because they can no longer access the Bitbucket content associated with their old login when using their new login, because they're separate Atlassian accounts. They can't just close their new account and change emails on the old one if they've created content (repos etc.) in the new one already.
In these situations it would be useful to be able to merge their old account into their new account so they have access to all their content from one account, at which point they can close their old account. |
See this discussion: https://community.atlassian.com/t5/Atlassian-Access-questions/how-to-transfer-my-transfer-atlassian-account-to-a-new-email/qaq-p/2328417#M4803
This is really important!