Download and customize the configuration mapping

Change how projects, configuration elements, and users get deployed

What makes the Configuration Manager for Jira (CMJ) Cloud a distinct admin tool is its ability to control how configurations will be deployed from one Jira Cloud site to another. You can decide how your projects, other configuration elements, and users will be deployed to the destination Jira Cloud site.

This powerful feature we built in CMJ Cloud allows you to:

• fix problems with source configuration elements like projects, custom fields, contexts, workflows, users, and more mid-deployment, and,

• transform the source configuration in the scope of the way you need it deployed to Jira Cloud.

This feature is called Customize mapping, and it’s an advanced version of the inline transformations available in CMJ Cloud’s UI. While there are limitations on where you can use certain inline transformations, you can customize the mapping of any project, configuration element, or user within the deployment scope. You can even make changes to how custom field contexts are gonna be deployed.

With Customize mapping, you can rename just about any configuration element and change the destination element it is mapped to. We're also giving you the option to download the current configuration mapping built by the analysis process with the Download mapping option. Keep in mind that the current mapping is always the latest mapping, and it will include any previous transformations you applied to the configuration.

Open

Download and customize the default configuration mapping

Once you add projects to your deployment and reach the analysis phase, you'll have the Download mapping and Customize mapping buttons. You'll spot them at the top right of the Analyze changes page in the deployment wizard. For the exact locations of the Download mapping and Customize mapping buttons, watch the gif below.

Open

With the Download mapping button, you'll get a JSON file listing the details of the deployed configuration elements and how they'll be deployed. Review the following example file for a better idea of what to expect. The file contains all elements in the deployment scope no matter their type - projects, users, custom fields, workflows, schemes, etc.

You can take this file and make changes to it or construct your own mapping file and apply it to the configuration. For this purpose, you need to upload a mapping file with transformations to the Customize mapping action. Check out the guidelines for customizing the configuration mapping.

Step-by-step guide for downloading and customizing configuration mapping

To customize the default configuration mapping:

1. Start a deployment.

2. On the Analyze changes page, click the Download mapping button on the top right.
   You will get a JSON file with the default mapping for all projects, configuration elements, and users in the deployment scope.

3. Modify the JSON file to correct problems or change the deployment option of an element. Check the guidelines about customizing the configuration mapping.

4. Click Customize mapping to upload the JSON file with the changes.

5. Review the number of changed elements in the dialog. If there are no elements with problems reported, click Confirm to apply the transformations from the file.
   The video below shows how to upload and apply custom configuration mapping.

6. Once you're done with the transformations, click Deploy to move on with the deployment.