Dave Meredith added a comment - 03/Feb/2025 4:57 PM This is useful for migrations however I don't think it addresses the problem that admins are trying to solve in Atlassian Cloud. Duplicate accounts happen a lot for a range of reasons... Even a common issue like name changes due to marriage will create a duplicate account when using IDP SCIM provisioning because the primary ID is the email address which usually changes. Without being able to merge these two accounts the only option is to delete a newly created duplicate and change the email address of the previous account that contained all of the history. If the duplicate isn't deleted / disabled it can even end up as an additional chargeable user in Atlassian Guard. I would need the ability to merge users that already exist in cloud with duplicate accounts that also exist in cloud.  

Akshay Johri added a comment - 25/Oct/2024 7:31 AM Hi. We had shipped the capability to Merge, Deduplicate or Deactivate users during migration using the Migration Assistants. Community Post :  https://community.atlassian.com/t5/Atlassian-Migration-Program/Merge-update-or-deactivate-users-during-your-transition-to-Jira/ba-p/2782592 Please try it and share your feedback. We're also looking at suggesting accounts with same  username  (but different email addresses) as duplicate accounts. Do you think it would be useful?

Akshay Johri added a comment - 25/Oct/2024 6:24 AM Hi. This is Akshay from Migrations team at Atlassian. We had shipped a capability to Merge, Dedup or Delete users during migration. Documentation:  https://support.atlassian.com/migration/docs/customize-your-users-in-advanced-experience/ Community Post:  https://community.atlassian.com/t5/Atlassian-Migration-Program/Merge-update-or-deactivate-users-during-your-transition-to-Jira/ba-p/2782592   Please let us know if this solves the bulk of the problem for you.

Akshay Johri added a comment - 09/Oct/2024 5:25 PM Hi. I’m Akshay, a Product Manager at Atlassian. We’ve introduced a new capability in the Jira Cloud Migration Assistant (JCMA) and Confluence Cloud Migration Assistant (CCMA) that helps manage your user base during a cloud transition. When running a migration, and trying to fix your user base, you can perform all complex changes in one go, by downloading the list of all users as a CSV. You can: Merge users : Combine duplicate accounts. Update email addresses : Correct any invalid email addresses. Deactivate users : Disable user accounts that are no longer required after migrating. Documentation: https://support.atlassian.com/migration/docs/customize-your-users-in-advanced-experience/ Community Post: https://community.atlassian.com/t5/Atlassian-Migration-Program/Merge-update-or-deactivate-users-during-your-transition-to-Jira/ba-p/2782592  

Anusha Rutnam added a comment - 04/Apr/2024 3:46 AM - edited I'm putting together an overview of the use cases mentioned in the comments and linked tickets here as I believe there are some cases where merge functionality is not required, and there may be confusion about what options are available. Terminology Atlassian account (Aa) - a user account with a unique ID and a unique email address. Atlassian accounts can be managed or unmanaged.  Individual - the real-life person who is conducting work in Jira Cloud. Each individual may have multiple email addresses and therefore multiple Atlassian accounts. Portal-only accounts - this is a concept in Jira Service Management projects only. Has associated Jira Cloud data - Can be true or false. For the purposes of understanding the use cases here I'm defining this as work in Jira that is associated with a specific user account e.g. if you add a comment or log work on an issue, or have assigned issues in Jira Cloud, that means you do have associated Jira Cloud data. Use cases       Scenario Possible solutions 1 [From the Description of this ticket] There are a number of situations where you want to delete a user [Aa 1] - but transfer all of their reported/assigned issues to someone else [Aa 2] . Perform a bulk update on all issues where Aa 1 is the reporter and assignee. Make Aa 2 the reporter and/or assignee instead. Documentation on bulk updates: Editing multiple issues at the same time   Note: It is not possible to update the author of a comment but we have a feature request: JRACLOUD-82191 Change comment's author from UI or Rest API 2 Merge Atlassian accounts and customer portal-only accounts to remove duplicates (or vice versa) Follow the steps here: Migrate a portal-only customer to Atlassian account 3 Would be very useful when Migrating from one Organization into another. Facing the Problem with duplicate Users after Migration Cloud to Cloud. Merge Users Function inside the "Migrate from Cloud to Cloud" with Domain mapping like "user@domain1.com" to "user@domain2.com" would also make Migrations a lot better.    More details on this scenario are required. If I understand correctly it seems like there are two Atlassian accounts for one individual and there should be one. It would be good to know if both accounts have associated Jira Cloud data that needs to be transferred to the one surviving account. 4 We changed domains and all of our users now have two accounts. They cannot update their personal user login and as the account owner, we also cannot edit this information even though the system tells the users we can. This is my understanding of this scenario:- Aa1: associated with old email address, but also with the individual's Jira history that needs to be saved. Aa2: associated with the new (desired) email address. Has no Jira history - the individual has not performed any actions while logged in using this account.   Follow the instructions in this article  under the subheading "If an unmanaged user has used their new email address with an Atlassian cloud product or website". Basically, the desired email address must be released so that it is available to be used on the account you wish to keep.   If either of the accounts is managed, there may be a few extra steps but getting the desired (new) email address associated with the desired (old) account should be doable. Could the watchers of this issue please provide other examples where they need the ability to merge users?

Anusha Rutnam added a comment - 04/Apr/2024 1:51 AM - edited Edit: I've reopened this ticket because I think there is a specific use case mentioned in the Description that is not covered in https://jira.atlassian.com/browse/ID-240 . I think there may be some related issues which I will link to here as I find them. Apologies for any confusion caused. Atlassian Update - April 2024 After some analysis, we've found that this ticket is a duplicate of the request ID-240 – Ability to merge Atlassian accounts to a single account with secondary emails which more votes recent updates from the product team workarounds We encourage you to watch and vote on the above instead. All internal ticket references on this ticket have been transferred. If you do not think this issue should have been closed, please add a comment here saying why and we can reopen it.

Yissachar Bar added a comment - 06/Mar/2024 9:29 AM 10 years and counting and people still need this feature.

Yev added a comment - 19/Sep/2023 2:30 PM This would be extremely helpful to merge Atlassian accounts and customer portal-only accounts to remove duplicates (or vice versa)

Piotr Nowak added a comment - 31/Jul/2023 9:01 AM Even wehen we split our enviroment i have 2 account  For now i cannot merge these.  For us is big issue on these time.

Alistair Thomson added a comment - 21/Jun/2023 8:49 AM We also need this feature please asap.