...
Yes, Configuration Manager for Jira will migrate them - they can be selected as part of the Create Snapshot Wizard - they all have dedicated steps - refer to https://botronsoftappfire.atlassian.net/wiki/spaces/CMJ/pages/478413782777316/Project+Snapshot for more details.
Will Configuration Manager for Jira migrate issues between instances?
...
Can I migrate Jira Service Desk projects with Configuration Manager for Jira?
...
Yes. Just update to CMJ version 6.0+.
- CMJ versions older than 6.0 can move projects of type Service Desk along with their related standard Jira configuration objects, but
...
- do not support any Service Desk – specific configurations (i.e. SLAs, queues, automation rules, etc. are not included in the snapshot).
After I migrated a Jira Service Desk project's standard configuration with Configuration Manager for Jira (prior to version 6.0), it is unusable through the UI.
After the SD project is deployed with CMJ, it may not function correctly, because its specific configuration is missing. To fix this, you can change the project type to another one (say Business) and revert it to Service Desk. This will force Service Desk to populate the necessary configuration for this project.
...
Configuration Manager for Jira allows this kind of deployment. Note that since version 6.0.0 Configuration manager no longer supports JIRA 6.x! For such cases use the latest 5.x version of CMJ.
However, there are things that should be kept in mind. Jira 7.x has introduced configuration objects that do not exist on 6.x and if you have them in the snapshot you’re deploying the deployment will fail. Most of the configurations are around permissions (manage workflow permission), security levels (application role levels) and visibility permission for filters/dashboards (logged in user). So, to do a successful deployment you’ll have to remove any usages of these items in the source project’s configuration. A good way to do this is to replicate their instance in a test environment and try the deployment a few times until you resolve all issues.
...
Configuration Manager is JIRA Server/Data Center only and is not available for JIRA Cloud. The development architectures are completely different and CMJ's primary focus is Server/Data Center.
That said, a common way to handle this is to restore the Cloud instance on a blank Server/Data Center instance, and then use Configuration manager to handle the projects migration.