Skip to end of metadata
Go to start of metadata

I have test, staging and production Jira instances. Do I need a commercial license for each of them?

The Configuration Manager for Jira license must match the license of Jira itself. Usually, you'll need commercial license only for the production instance. Once you purchase a Configuration Manager for Jira license, you'll be able to generate development licenses for your test and staging instances.

If you have a commercial CMJ license, you can obtain dev licenses from my.atlassian.com as described here: https://www.atlassian.com/licensing/purchase-licensing?_ga=1.167884517.53990726.1485781377#licensing-7

My trial license for Configuration Manager for Jira has expired. What should I do?

If you haven’t used all 3 trial licenses on your test instance you can just get a new one from Atlassian’s marketplace using the “Try it free” button - https://marketplace.atlassian.com/1211611 or from my.atlassian.com.

If you’ve used all 3 trial licenses, open a request at our support portal https://support.botronsoft.com and we'll assist you further.

Will Configuration Manager for Jira migrate filters, Agile boards and dashboards between instances?

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://botronsoft.atlassian.net/wiki/spaces/CMJ/pages/4784137/Project+Snapshot for more details.

Will Configuration Manager for Jira migrate issues between instances?

Yes, Configuration Manager for Jira supports issues since version 5.0.

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.

Is it possible to use Configuration Manager for Jira to migrate a Jira project (with issues, filters, dashboards, Agile boards, attachments) if the source system is Jira Software 7.x and the destination system is Jira 6.x with Agile?

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.

That being said, if possible, we strongly advise you to first upgrade the target instance to at least the same version as the source. This would make the process much easier.

Can Configuration Manager for Jira migrate between Jira Cloud and Jira Server/Data Center and vice versa?

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.

  • No labels