Differences between CMJ Server/Data Center and CMJ Cloud
On this page:
- 1 Comparison
- 1.1 Feature
- 1.1.1 Jira application support
- 1.1.2 Deployment of configuration elements
- 1.1.3 Configuration analysis
- 1.1.4 Transformations/Selective Merge
- 1.1.5 App data and configuration deployment
- 1.1.6 Integrity Check
- 1.1.7 REST API Automation
- 1.1.8 Rollback
- 1.1 Feature
Comparison
If you're a Jira Server/Data Center user transitioning to Jira Cloud and using Configuration Manager, you'll have to migrate to Configuration Manager for Jira Cloud.
Check out the table below for a breakdown of the features in Configuration Manager for Server/DC versus Configuration Manager for Jira Cloud. It provides insights into the following features:
AVAILABLE - features that have already been rolled out,
NOt available - features not planned for the future,
COMING SOON - features currently in development, and
FUTURE - features planned for the future.
Need more details on the differences between Configuration Manager for Jira and Configuration Manager for Jira Cloud? Feel free to reach out to our support team for assistance.
Feature | Configuration Manager for Server/DC | Configuration Manager for Cloud |
Jira application support | ||
Jira Core configuration | available | available |
Jira Software configuration | available | available |
Jira Service Management configuration | available | coming soon |
Deployment of configuration elements | ||
Boards Selecting boards to deploy | available | available |
Boards associated with the deployed project Automatically adding such boards to the deployment | available | future |
Filters | available | future |
Dashboards | available | future |
Issue data and attachments | available | future |
Filtering issues to deploy with JQL | available | future |
Configuration analysis | ||
Analysis report of the deployed configuration | available | available |
Detailed analysis of the deployed configuration In the detailed analysis, we display actual changes like a project scheme changing from X to Y, adding a custom field to a screen, or adding a post function to a workflow. | available | future |
Audit log | available | future |
Transformations/Selective Merge | ||
Renaming configuration elements inline | available | available* Inline rename is available for projects, workflows, workflow, and issue type schemes and filters. Changing project keys is available, too. |
Change mapping between source and destination configuration elements | available | coming soon |
Custom field conflict resolution | available | coming soon |
Modification of active workflows and workflow schemes with issue migration | available | future |
User mapping | NOt available | coming soon |
Group mapping | NOt available | future |
App data and configuration deploymentDeploying 3rd-party Jira apps' configuration and data between Jira instances | ||
Workflows | available | available |
Custom fields and projects | available | future |
App configuration that is not project-related | available | future |
Integrity Check | ||
Integrity check of the deployed configuration | available | future |
Built-in integrity check UI | available | future |
Built-in Power Admin | available | NOt available |
REST API Automation | ||
Public REST API | available | NOt available |
Rollback | ||
Rollback of configuration changes | available | NOt available |