Uploaded image for project: 'Migration Platform'
  1. Migration Platform
  2. MIG-208

Map with existing entities even if the record is not found while migrating using Jira Cloud Migration Assistant

XMLWordPrintable

    • 56

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Problem Definition

      Currently, as per this KB, if there is no record of the entity in the JMT then it remigrates it by adding name(migrated).

      Suggested Solution

      There are customers who want to use the plugin for migrating projects in the Cloud site
      with existing data and this data can have entities common to the ones in the migration plan.
      The plugin should link such entities with the existing ones rather than creating a new field.
      OR an option can be provided to the customer if they want to link to an existing entity or remigrate it.

      Workaround

      NA

            [MIG-208] Map with existing entities even if the record is not found while migrating using Jira Cloud Migration Assistant

            Radhika Patodiya (Inactive) added a comment -

            Update: 05/08/2021

            We've started work for fixing this issue entity by entity. We've already rolled out the fix for following config entities:

            • Issue status
            • Priority
            • Resolution
            • Issue type link
            • Project category
            • Project role

            The fix will prevent unnecessary duplication and link the new config entities to the existing ones, if they are identical.

            More details can be found on this page: https://support.atlassian.com/migration/docs/how-the-jira-cloud-migration-assistant-links-your-data/

            Radhika Patodiya
            Product Manager, Atlassian Cloud Migrations

            Radhika Patodiya (Inactive) added a comment - Update: 05/08/2021 We've started work for fixing this issue entity by entity. We've already rolled out the fix for following config entities: Issue status Priority Resolution Issue type link Project category Project role The fix will prevent unnecessary duplication and link the new config entities to the existing ones, if they are identical. More details can be found on this page: https://support.atlassian.com/migration/docs/how-the-jira-cloud-migration-assistant-links-your-data/ Radhika Patodiya Product Manager, Atlassian Cloud Migrations

            Christian Domsch added a comment -

            This is especially important if you migrated first with the site import and then want to migrate additional projects manually with the JCMA. In this case, the JCMA has no mapping to begin with and the projects migrated now will all have duplicated entities, as they all already exist from the site import.

            Christian Domsch added a comment - This is especially important if you migrated first with the site import and then want to migrate additional projects manually with the JCMA. In this case, the JCMA has no mapping to begin with and the projects migrated now will all have duplicated entities, as they all already exist from the site import.

              14ede9477001 Radhika Patodiya (Inactive)
              sali@atlassian.com Saif
              Votes:
              12 Vote for this issue
              Watchers:
              28 Start watching this issue

                Created:
                Updated: