Update: Please head over to https://jira.atlassian.com/browse/MIG-169 to vote and comment for this feature.

Summary

The What gets migrated with the Jira Cloud Migration Assistant documentation has a section called What isn't migrated pointing out that Cross-project boards doesn't get migrated. As stated in How do I get a board to point to multiple projects, it is possible to make a board available cross-project, which is widely leveraged in Server environments.

Suggestion

To enhance Jira Cloud Migration Assistant (JCMA) so it does migrate cross-project boards or to have a validation rule that states to administrators which boards will need to be manually re-created in Cloud once the migration is completed.

Current Scenario

Administrators have no visibility to which boards will not get migrated until they migrate and start to notice missing data in Cloud. This is not a reliable process.

Expected Scenario(s)

• Administrators are presented with a message in the migration plan (or in the logs) stating which boards are not migrated.
• Administrators can select one project to tie the board(s) and get them migrated.
• Administrators can migrate all boards regardless.