Issue Summary

Some times we see project export errors related to lingo Translation field ID while executing JCMA preflight checks at data preparation stage like below:

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]

Once we fix this error and retry the migration, it again fails and we see similar error for different field and request type. Something like:

2025-03-19 23:12:03.001236 ERROR <Pkey> project-export mri:mig:jira/servicedesk:lingoTranslationFieldUpdate:2222 has reference to requestType with id 444 that was expected to be exported but was not. [JCMA 510]

Once we fix the error and reattempt we see the same behavior. This pattern continues untill we resolve all errors one by one. This process can be inefficient for users, as it requires multiple iterations to resolve all issues.

Steps to Reproduce

1. Create a project and corrupt the data by deleting some of the issue type id's in the database.
2. Include this project in the migration plan and execute the preflight checks
3. Wait for the error to occur related to custom lingo translation filed update ID.

Expected Results

JCMA should log all the errors in single project export log file this would enable users to address all export errors in one go.

Actual Results

It reports error one by one as we continues to resolve them.

Workaround

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