Deploy configuration changes from Jira Cloud to Cloud

Owned by Comala Publishing for Confluence Cloud
Last updated: May 21, 2024 by Julver Petrova (Deactivated)
4 min read

On this page:

Deploy project configuration changes from Jira Cloud to Cloud

Configuration Manager for Jira (CMJ) Cloud helps you deploy project configuration changes from one Jira Cloud site to another. This article will refer to this use case as "Cloud-to-Cloud".

To accomplish this use case, you need to create a temporary Jira Cloud site. It can be either a Jira Cloud site or a sandbox provided by Atlassian for testing purposes.
Learn more about setting up Atlassian sandboxes.

CMJ Cloud is built to protect the integrity of the destination Jira Cloud site by blocking breaking changes. The app analyzes each change that will be introduced. It then identifies the ones that aren't compatible with the destination Jira Cloud's project configurations.

 

The video below demonstrates a configuration deployment from one Jira Cloud site to another (cloud-to-cloud) with Configuration Manager for Jira Cloud.

CMJC-cloud-to-cloud-successful-deployment.mp4

Use case steps

This section will guide you through the Cloud-to-Cloud use case's prerequisites and implementation phases.

Prerequisites

  • Destination Jira Cloud site

  • Source Jira Cloud site: a Jira Cloud site or an Atlassian sandbox, which are replicas of the destination Jira Cloud site. Learn more about setting up a sandbox.

  • Licenses: You need a paid license for the CMJ Cloud app on the destination Jira Cloud site and a development license/trial license for CMJ Cloud on the source Jira Cloud site/sandbox.

  • Supported objects: Make sure CMJ Cloud supports the configuration elements you want to upload to the destination Jira site along with your projects. See the Supported Configuration Elements document.

  • Apps: Any apps used to configure objects in the source Jira Cloud site/sandbox must also be installed on the destination Jira Cloud site.

High-level process

This section lists the high-level phases of implementing the Cloud-to-Cloud use case. To learn more about each phase, read our Detail process guide below.

  • Setup: Set up а temporary Jira Cloud site or a sandbox, a replica of the destination Jira Cloud site. Learn more

  • Phase 1: Either restore the destination configuration to the source Jira Cloud site or copy the destination Jira Cloud site to the sandbox. Learn more

  • Phase 2: Make configuration changes to the source Jira Cloud site/sandbox. Learn more

  • Phase 3: Conduct user acceptance testing of the configuration changes on the test Jira Cloud site/sandbox. Learn more

  • Phase 4: Deploy projects and related configuration elements from the test Jira Cloud site/sandbox to the destination Jira Cloud site. Use CMJ Cloud for this purpose. Learn more

Detailed process

Review the diagram and detailed guide below to understand the use case better and implement it.

 

 

Setup

  • Set up a source Jira Cloud site/sandbox and install the CMJ Cloud app on it.

  • Install CMJ Cloud on your destination Jira Cloud site.

  • License CMJ Cloud. License CMJ Cloud with a dev license on the source Jira Cloud site/sandbox. License CMJ with a paid license on the destination Jira Cloud site.

    Phase 1: Replicate the destination Jira Cloud’s configuration to the source Jira Cloud site/sandbox

  1. Restore the destination site’s configuration to the source Jira Cloud site or copy the destination site's data to the sandbox. Learn more about copying data to the sandbox.

    Phase 2: Make configuration changes to the source Jira Cloud site/sandbox

  2. Make desired changes to projects and configuration elements. Follow the deployment process described here.

    Phase 3: Test the configuration changes on the source Jira Cloud site/sandbox

  3. Get stakeholders involved in user acceptance testing in this phase to confirm the proposed changes are operating as expected.

    BY unexpected behavior If the configuration changes don't meet stakeholders' expectations or the proposed changes are causing unexpected behavior, make changes in the source Jira Cloud site/sandbox. Then, start the use case from the beginning (Phase 1).

    Phase 4: Deploy projects to the destination Jira Cloud site

  4. Deploy the projects and their related configuration elements from the source Jira Cloud site/sandbox to the destination Jira Cloud site using CMJ Cloud. Follow the deployment process described here.

  5. (optional) Retire the source Jira Cloud site/sandbox.