Issue Summary

Currently, when performing a Server-to-Cloud migration that includes Jira Software projects and Jira Software management projects, the CMA app will not check if those products are active and available in the destination Cloud site, leading to failed or partially migrated migrations.

Steps to Reproduce

1. Set up a Jira Server instance with Jira Software and Jira Service management projects
2. Set up a Cloud site but do not activate Jira Software and Jira Service management
3. Create a new JCMA migration from Server to Cloud
4. Select Software Project and JSM project types to be migrated

Expected Results

Similar to the existing checks for Apps and user tiers, JCMA should warn you that some of the project's functionalities might be impacted or lost due to missing products on the Cloud site.

Actual Results

1. There is no error or warning from JCMA letting you know that the migration won't be successful due to the lack of products in Cloud. JCMA allows you to proceed with the migration without checking the necessary applications to fulfill the migration to the appropriate project type.

The below exception is thrown in the migration log file:

2022-01-12 14:34:12.139 ERROR SP project-import We couldn't import Permission Scheme 'Default software scheme'. Reason: IllegalArgumentException: Project permission [MANAGE_SPRINTS_PERMISSION] does not exist. This caused 2 other items to fail. 

Sprints are a Jira Software feature so it’s expected that this fails. However, one could argue JCMA should check this ahead, since having Jira Software in the Cloud is a must-have in this case.

Workaround

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