-
Bug
-
Resolution: Fixed
-
Highest
-
None
-
JCMA - 1.7.1
-
None
-
20
-
Severity 3 - Minor
Issue Summary
When the customer tries to migrate Projects from Jira server to Jira Prod cloud site using Jira Migration Assistant, Project migration fails with an Error.
Steps to Reproduce
Not applicable for all the migration scenarios.
The basic step to rep-produce is to migrate the project from Server to Cloud using Jira Migration Assistance.
Expected Results
The project should migrate successfully.
Actual Results
The below exception is thrown in the xxxxxxx.log file:
2020-05-06 19:54:51,679+0100 pool-10-thread-1 INFO [c.a.j.m.tracking.polling.StatusPoller] Migration aaaaaaa-12345-67890-bbbbb-cccceeee completed, Migration errors: projectDataUpload#ABC: java.lang.IllegalStateException: More than one migrated file found for attachment 111111 (StackTrace=java.lang.IllegalStateException: More than one migrated file found for attachment 111111 at com.atlassian.jira.migration.migration.MigratedFileRepository.findMigration(MigratedFileRepository.kt:69) at com.atlassian.jira.migration.workers.AttachmentMediaIdService$generateAttachmentMediaIdsForProject$2.invoke(AttachmentMediaIdService.kt:43) at
More than one migrated file found for attachment XXXX
Workaround
Please do reach out to the Atlassian support to confirm if you should Delete or truncate the table. The workaround is to delete or truncate the AO_6FF49D_MIGRATED_FILE table prior to migrating to the production site. This can be done using either of the SQL below:
DELETE FROM AO_6FF49D_MIGRATED_FILE
// or
TRUNCATE TABLE AO_6FF49D_MIGRATED_FILE