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 a 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.
I am using the trial license of Configuration Manager for Jira. Do I have access to all features available with the commercial license?
Yes, the trial license gives you access to the whole functionality of CMJ. The idea of our trial license is to test and see for yourself if CMJ satisfies all your needs.
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 or from my.atlassian.com.
If you’ve used all 3 trial licenses, open a request at our Support Portal and we'll assist you further.
What kind of licenses do I need for migrations?
Otherwise, both source and target instances should be licensed using commercial licenses. If any intermediate servers are used as clones, they can use the development licenses that come with the commercial licenses. For migrations or other short-term needs, you can use 1-month commercial licenses issued by Appfire.
If you need licenses for migrations, please open a request at our Support Portal and we'll assist you further.
What kind of licenses do I need for short-term purposes?
The minimum license duration for licenses issued through the Atlassian Marketplace is one year. However, for migrations and short-term needs, Appfire can issue licenses directly, minimum for a 1-month duration. The cost of a one-month license is 20% of the yearly price for the same user tier. If you need a short-term license, please open a request at our Support Portal and we'll assist you further.
Will Configuration Manager for Jira migrate filters, Agile boards, and dashboards between instances?
Will Configuration Manager for Jira migrate issues between instances?
Yes, Configuration Manager for Jira supports issue data since version 5.0. CMJ handles everything related to issues, including attachments, worklog, issue links, issue history, ranking, sprints, reports, and more.
Are my entire configuration and all the issues within going to be moved to production automatically using Configuration Manager for Jira?
Yes. The entire configuration, captured in the configuration snapshot, will be rolled out. All the issues to the selected projects as well. Some apps configuration and data which are not supported by Configuration Manager for Jira won't be moved. The supported objects are listed here.
Can I move projects from a server with a newer server instance to an older server instance?
It is strongly recommended that both production servers are on the same version. The opposite adds unnecessary complexity.
Can I use different Configuration Manager versions to create a snapshot and later deploy it to the target instance?
The Configuration Manager version on the target instance needs to be the same or newer than the one used to create the snapshot.
How long does it take to move multiple projects?
Depending on the user management normalization, the amount of data, and the other analysis, it can take anywhere from several hours to a few weeks.
Can custom app data be moved using Configuration Manager?
Yes. Configuration Manager can be extended to handle any custom apps.
Can I migrate Jira Service Management projects and all their configuration with Configuration Manager for Jira?
Yes, since CMJ 6.0. Jira Service Management is officially fully supported since CMJ version 6.0. You can move Service Management projects with their related standard Jira configuration objects,Jira Service Management-specific configuration, and issue data. CMJ versions older than 6.0 do not support any Service Desk–specific configuration (i.e. SLAs, queues, automation rules, etc. are not included in the snapshot). Learn more by reading our Jira Service Management document.
Is it possible to use Configuration Manager for Jira to migrate a Jira project (with issues, filters, dashboards, Agile boards, and 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.
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 configuration and data between Jira Cloud and Jira Server?
Configuration Manager is Jira Server only and is not available for Jira Cloud. The development architectures are completely different and CMJ's primary focus is Server. That said, a common way to handle this is to restore the Cloud instance on a blank Server instance, and then use Configuration manager to handle the project migration. See more details in our detailed Use Case documentation.
Can Configuration Manager for Jira migrate 3rd party app configuration?
Yes, Configuration Manager supports some of the apps natively and for the rest of the apps enables vendor-supplied integrations. We designed and developed a great module called Service Provider Interface that allows app vendors to integrate their apps with Configuration Manager. If you are an app vendor and would like to allow your customers to transfer your app’s custom configuration and data between Jira instances seamlessly, you can read how to make the integration real in our documentation.
Our goal is to allow the admins to seamlessly handle the entire configuration of Jira and its great apps. You can find more information about Configuration Manager’s support for apps at Apps Integrations.
Does Configuration Manager for Jira send data outside of the Jira system it is installed on?
No. Configuration Manager for Jira operates only on the system it is installed on and doesn't send any data to the Internet.
Integrity Check for Jira and Power Admin empty license keys
With Configuration Manager for Jira version 6.9.0, the Integrity Check and Power Admin apps appear unlicensed. If you have a license for Configuration Manager, no need to worry, this means that the Integrity Check and Power Admin apps are licensed as well, although an empty license key is shown on the Manage apps page. The Integrity Check for Jira and Power Admin apps are included in Configuration Manager at no additional cost. Learn more