-
Suggestion
-
Resolution: Unresolved
-
None
-
14
-
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
- is related to
-
MIG-1215 Add option for Confluence Migration assistant to migrate attachments after data migration
- Closed
-
MOVE-104546 Loading...
- relates to
-
MIG-1829 Add ability for Jira Cloud Migration Assistant to migrate attachments after project migration
- Gathering Interest
- mentioned in
-
Page Loading...