Jira Cloud Migration Assistant will not import the IDs from deleted statuses, leaving the issue history tab with broken references

Summary

Tickets that do not contain the source/destination Status ID on the history tab will cause the "My requests" (customer portal) page to not retrieve issues and be not interactive. This is caused by Jira Cloud Migration Assistant not importing the status ID of statuses deleted on the Server instance.

Steps to Reproduce

1. On a server instance, create a new project.
2. Create a new issue and transition it through a few different statuses. (Example To do > Pending > In Progress > Done)
3. Remove one of those statuses from the associated workflow and delete it.
4. Note that even after deleting the status, the issue history tab will keep a record of the Status name and ID.
5. Migrate the project to Cloud via Jira Cloud Migration Assistant.

Expected Results

• All the issues, statuses, and references are preserved.

Actual Results

The id of the status deleted on the Server instance will not exist on the issue history.

Notes

This bug will cause several side effects on JSM portal, such as:

• Affected issues will prevent the JSM Customer portal from loading tickets on the "Requests" page.
• Affected issues will not load on the portal.
• The "Manage columns" feature of the portal will break.

Impact on apps

When using the /rest/servicedeskapi/request/{issueId}/comment REST API on affected issues, the request will fail with a 500 - Internal Server Error message.

The corresponding error message (only visible to Atlasssian staff) is:

Caused by: com.atlassian.jira.util.dbc.Assertions$NullArgumentException: id should not be null!
	at com.atlassian.jira.util.dbc.Assertions.notNull(Assertions.java:24)
	at com.atlassian.jira.util.dbc.Assertions.notBlank(Assertions.java:121)
	at com.atlassian.jira.config.DefaultStatusManager.getStatus(DefaultStatusManager.java:276)
	at com.atlassian.servicedesk.internal.feature.customer.request.activitystream.providers.StatusAndResolutionActivityProviderImpl.getStatusNameForCustomer(StatusAndResolutionActivityProviderImpl.java:165)
...
at com.atlassian.servicedesk.api.rest.resource.CommentResource.createRequestComment(CommentResource.java:102)

Workaround

Reach out to the customer support team for help to update any missing entry newvalue and oldvalue on the changeitem table with a dummy id or copy correct ids from the correspond table on the server