Issue Summary

The Jira preflight checks fail at data preparation stage while exporting Custom lingo translation field update ID due to invalid request type ID (JCMA 510 code):

2025-03-19 08:04:08.907584 ERROR <Pkey> project-export mri:mig:jira/servicedesk:lingoTranslationFieldUpdate:1111 has reference to requestType with id 333 that was expected to be exported but was not. [JCMA 510]

The requesttypes are not exported due to the non-existing issuetype IDs and hence the above error.

Steps to Reproduce

1. Create a Jira service management project with issue types and request types
2. Add the custom lingo translation fields.
3. Corrupt the data by deleting some of the issue types that refers to the request types.
4. Create migration plan, include the project and execute preflight checks. Wait for it to fail at data preparation stage with above error.

Expected Results

JCMA should check the relation: request type -> issue type to filter out the translations instead of just relying on the request type existence.

Actual Results

The preflight check fails at data preparation stage with below error [JCMA 510]:

2025-03-19 08:04:08.907584 ERROR <Pkey> project-export mri:mig:jira/servicedesk:lingoTranslationFieldUpdate:1111 has reference to requestType with id 333 that was expected to be exported but was not. [JCMA 510]

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available. Please contact Atlassian Support.