Deployment Flow

Owned by Rosen Marinkov
Last updated: May 07, 2024 by Julver Petrova
4 min read

On this page:

Deploy project configurations from one Jira Cloud site to another

CMJ Cloud offers automated configuration deployments from Jira Cloud to Cloud. You can deploy whole projects and their configuration elements from one Jira Cloud site to another. You can also introduce changes to projects and configuration elements in the destination Jira Cloud sites.

CMJ Cloud protects the integrity of destination Jira Cloud sites by blocking deployments with high-risk configuration changes. It was intentionally built to detect and report configuration problems and ultimately prevent breaking changes.

What Jira Cloud configuration are we able to deploy?

See the complete list of supported configuration elements we’re able to deploy today.

How to deploy project configurations between Jira Cloud sites

To deploy project configurations with CMJ Cloud, follow the steps below:

  1. Install the Configuration Manager for Jira (CMJ) Cloud app on your source and destination Jira Cloud sites. The source site can be a sandbox or another Jira Cloud site.

  2. Log in to your source Jira Cloud with Site admin or Organization admin permissions.

  3. Navigate to Apps > Configuration Manager > Authorization page to authorize first.

  4. Provide an Atlassian API token for your account. Learn more about using an API token.

  5. Navigate to the Apps > Configuration Manager > Configuration Deployment page.
    If you haven’t started any deployments yet, you’ll see two New deployment buttons on the page.

  6. Click either of the New deployment buttons.

  7. On the Connect phase, name your deployment and provide the destination Jira Cloud’s URL (step 1 in the screenshot below).

  8. Click the Select button to pick the projects you want to add to the deployment (step 2 in the screenshot above).

  9. Select the projects you want to deploy using the Add projects to the deployment link (step 1 in the screenshot below).

  10. (Optional) To add boards to the deployment scope, click the Add boards to the deployment (step 2 in the screenshot above).
    The boards associated with the projects in the scope won’t be automatically added to the deployment. You need to select the boards you want to include manually.

  11. After adding projects and boards to the deployment, click Analyze to move to the Analyze changes page.

  12. In the Analyze phase, review the report of the changes introduced to the destination Jira Cloud. The Analyze changes page of the wizard shows you the project configurations, configuration elements, and users deployed to the destination. Learn more about how users are deployed with CMJ Cloud.
    CMJ Cloud doesn't deploy projects’ issues yet.

  13. CMJ Cloud also detects and shows warnings and errors. Remember that warnings won't block deployments, but errors will.

    You can use the Rename and Change key (for projects) buttons to fix conflicts between the source and destination configuration. You'll find these quick fixes in the conflict message itself. Learn more about all the transformations you can apply to the configuration.

  14. After resolving the errors, you may need to start the deployment from the beginning, or you can rerun the analysis to check for any new errors.

  15. If the new analysis detects no errors, you can click the Deploy button to run the deployment.

  16. After the deployment is completed successfully, you can review a summary of the results in the Deployment summary table (see the screenshot below).

  17. Navigate to the destination Jira Cloud site to browse your new or updated projects, custom fields, workflows, etc.
    The source Jira Cloud site’s projects and the configuration elements related to them will still be present and unchanged.