-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
16
-
Scenario:
Data preparation checks fail with an unclear error message in the migration log.
Current log
2024-01-12 16:21:22.341 ERROR PROJA project-export We couldn't export Issue PROJA-351. Reason: java.lang.IllegalStateException: Entity mri:mig:jira/classic:issueSecurityLevel:10010 is expected to be exported, but it was not. [JCMA 000]
Proposed log
2024-01-12 16:21:22.341 ERROR PROJA project-export We couldn't export Issue PROJA-351. Reason: java.lang.IllegalStateException: Entity mri:mig:jira/classic:issueSecurityLevel:10010 is expected to be exported, but it was not. [JCMA XYZ] Use the troubleshooting page to fix this error. Open the troubleshooting page using the URL below and use the error code (starts with “JCMA”) from the error to locate the fix in the troubleshooting page. https://support.atlassian.com/migration/docs/troubleshoot-migration-with-jira-cloud-migration-assistant/#Data-preparation-errors
- relates to
-
MOVE-1750488 You do not have permission to view this issue
Just tried test migration to Cloud and end with same issue...
2024-12-10 09:30:07.152982192 ERROR DP project-export We couldn't export Issue DP-495. Reason: java.lang.IllegalStateException: Entity mri:mig:jira/classic:issueSecurityLevel:10300 is expected to be exported, but it was not. [JCMA 000]
2024-12-10 09:30:07.798484400 ERROR DP project-export We couldn't export Issue DP-496. Reason: java.lang.IllegalStateException: Entity mri:mig:jira/classic:issueSecurityLevel:10300 is expected to be exported, but it was not. [JCMA 000]