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

Jira Cloud Migration Assistant does not migrate historical changes to an issue's project key

XMLWordPrintable

    • 1

    • 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.

      Issue Summary

      If you move an issue to a new project and migrate both the original and new projects from Server to Cloud using the Jira Cloud Migration Assistant app, there will be no history of the project change on the destination Cloud site. Users are unable to search for the ticket in the new project using the original issue key nor are they able to use any URLs referencing the old key to be redirected to the new project.

      Steps to Reproduce

      1. Move issue from project A to project B
      2. Migrate project A and project B from Server to Cloud using JCMA

      Expected Results

      Activity tab shows change in project and issue key
      URLs with old issue key redirects to new issue key
      Searching for old issue key returns new issue key

      Actual Results

      No mention of change to project or issue key in activity tab
      URLs with old issue key do not redirect
      Searching for old issue keys do not return new issue key

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

        1. Screen Shot 2020-08-12 at 5.42.50 PM.png
          Screen Shot 2020-08-12 at 5.42.50 PM.png
          360 kB
        2. Screen Shot 2020-08-12 at 5.43.48 PM.png
          Screen Shot 2020-08-12 at 5.43.48 PM.png
          390 kB

            [MIG-238] Jira Cloud Migration Assistant does not migrate historical changes to an issue's project key

            Dilan Weerasinghe added a comment -

            JCMA 1.4.3 GA Release fixed this issue.

            Dilan Weerasinghe added a comment - JCMA 1.4.3 GA Release fixed this issue.

            Jason Wong added a comment -

            Update August 25th 2020 - reclassification from Bug to Suggestion

            We are changing this from a bug to suggestion due to this problem arising not from an error / regression, but due to the migration not currently supporting the the migration of Confluence links.

            In general, data that is currently unsupported by the Jira Cloud Migration Assistant is documented on this page: [What gets migrated with the Jira Cloud Migration Assistant|https://confluence.atlassian.com/cloud/what-gets-migrated-with-the-jira-cloud-migration-assistant-993925216.html]

            This does not change the status or prioritisation of the Atlassian teams solving this particular problem.

             

            Jason Wong

            Product Manager, Atlassian Cloud Migrations

            Jason Wong added a comment - Update August 25th 2020 - reclassification from Bug to Suggestion We are changing this from a bug to suggestion due to this problem arising not from an error / regression, but due to the migration not currently supporting the the migration of Confluence links. In general, data that is currently unsupported by the Jira Cloud Migration Assistant is documented on this page: [What gets migrated with the Jira Cloud Migration Assistant| https://confluence.atlassian.com/cloud/what-gets-migrated-with-the-jira-cloud-migration-assistant-993925216.html ] This does not change the status or prioritisation of the Atlassian teams solving this particular problem.   Jason Wong Product Manager, Atlassian Cloud Migrations

              d64d1edffe88 Oleg Timoshenko
              hbui Houston B.
              Votes:
              1 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: