Summary

JCMA migration may fail with the error:

2024-06-12 16:57:07.715549 ERROR ABC project-export We couldn't export Issue ABC-174. Reason: java.lang.NullPointerException. [JCMA 000]

This error is found in the report after the migration fails.

Expected Results

The error report should indicate what the actual problem is to unblock the migration and allow it to succeed

Actual Results

The error log atlassian-jira-migration.log contains the following additional details:

2024-06-12 16:56:20,892+0000 pool-150-thread-2 ERROR user 851x30906x1 11f2wvz /rest/migration/latest/check/123abc2871e249634310cf36d16ea92ff038 [c.a.j.m.export.framework.DefaultExportFailureHandler] 37f4171eec2871e249634310cf36d16ea92ff038: Exporting entity Issue ABC-147 failed
java.lang.NullPointerException
	at com.atlassian.jira.migration.export.core.issue.IssueExporter.hasValidIssueStatusInWorkflow(IssueExporter.kt:571)

The log indicates a null value found when trying to validate the issue status.

Recommendation

The JCMA error report should provide more details about the actual problem instead of a generic JCMA 000 message. In this case, the error is that there is a missing issue status during the project export. This error will block the project export, causing the migration to fail.

User Workaround

Based on the error, the problem is that the issue is missing an issue status.

select * from jiraissue where issuestatus is null;

To correct the problem, you can add an issue status to the specific issue from the UI.