Problem Definition

According to https://support.atlassian.com/migration/docs/what-gets-migrated-with-the-jira-cloud-migration-assistant/ Jira cloud migration assistant migrates the custom field type Project picker (single project) containing the custom field value within same project key.

But if the custom field contains Cross-project key values then affected Jira issues are not migrated to cloud.
JCMA log:

JCMA error log:
2022-02-02 17:32:43.326 ERROR *SOFB* project-import We couldn't import Issue SOFB-4 because of 1 missing dependencies: *Project* *SOFK*. This caused 2 other items to fail. Check the reasons for the missing dependencies on your server site.

Steps to reproduce

1. Create project A
2. Create project B
3. Create a custom field type Project picker (single project) assign it to both project A, B and to all screens
4. Create issue1 on project A with custom field type Project picker (single project) referring to project A
5. Create issue2 on project A with custom field type Project picker (single project) referring to project B
6. Migrate project A and project B together (or) Project A alone to cloud site using Jira cloud migration assistant.
7. Jira cloud migrates only the issue1 custom field containing the value of (Project A key). Issue2 migrates without any custom field value.

Suggested Solution

• JCMA should provide a post-migration report that custom field values containing the different project keys are not migrated.
• JCMA should migrate the custom fields of both projects when project A and project B migrated altogether.

Workaround

Import the missing data using CSV method.