Hello. We tried to migrate one of our projects from Jira cloud SANDBOX to the Jira cloud PRODUCTION, using Jira cloud assistant. Despite the schemes and custom fields had the same titles in both instances --> JCMA creates duplicated schemes and custom fields. It duplicates the scheme and renames it with (migrated) word in the brackets. The same with custom fields - they are all duplicated.
Is there any way how to avoid these duplicities?
Hi @Lucie Mlčáková ,
Welcome to Atlassian community!
In the C2C migration, all the scheme and other configuration will be duplicate name If that name already exist in the target cloud site So If you want to remove the Duplicate word from the fields and others then you can directly connect with Atlassian Migration team to remove that word.
Note :- In migration, If the same name already exist in the target site then migration entity will create a new one and add the duplicate word in the field end
Regards,
Sanjen Bariki
@Sanjen Bariki I believe that the duplicated entity has the same name with the word "(migrated)" appended to the name, not the word "duplicate".
@Lucie Mlčáková I think for now, if it is just for one project, you can merge the duplicate entities manually with the original entities (i.e. change the configuration of the migrated project to use the original entities instead of the duplicated entities, if they are exactly the same) in Jira Cloud production and then delete the duplicate entities after making sure they are no longer attached/linked to any of the projects or their configuration entities.
In order to avoid this in future, make sure to go through the migration documentation of Jira Cloud-to-Cloud migration feature to ensure that this is the expected behavior of migration. If not, then make sure that the properties of the configuration entities with the same name are also exactly the same in both the source and the target Cloud sites otherwise the duplicate entities will still be created by the migration.
I hope this helps!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Taranjeet Singh ,
Thanks for the clartification on it @Taranjeet Singh .
Agreed.
Regards,
Sanjen Bariki
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.