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

Adding ability for Jira Migration Assistant (JCMA) to migrate attachment after data Migration

XMLWordPrintable

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

      When we Migrate Project using Jira Migration assistance, The data gets migrated for all the projects first and then attachments are migrated.

      Some time the Attachment Migration fails and in order to restart the migration, We need to Delete the project and then re-migrate, However, Some time it is not a feasible solution for the customer. 

      So, If we have a way to migrate only attachment after migration of data using Jira Migration Assistant it will be helpful.

      Why this is important

      • In some scenarios, users notice the broken attachments days/weeks after the migration. New issues have been created and it's not possible to delete the project to just re-migrate the attachments.
      • Project deletion is taking very long if the project contains thousands of issues. This is causing delay on the planned migration timeline.

      Workaround

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

              Unassigned Unassigned
              sp@atlassian.com SriKumar P (Inactive)
              Votes:
              4 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: