Analyze changes

Analysis of configuration changes to destination Jira Cloud

After CMJ Cloud finishes analyzing the project configurations and the elements associated with them, it presents a detailed report of the changes that will be introduced to the destination Jira Cloud site.

The analysis report contains the following information:

• Counters of the configuration elements being deployed. Learn more

• Projects that are being deployed. Learn more

• Configuration elements that are being deployed. Learn more

• Users in the deployment. Learn more

The sections below explain the information presented in the Analyze changes phase of the deployment.

Open

Configuration counters

The configuration counters on the Analyze changes page show the number of configuration elements of a given type that will either be added, modified, or present errors on the destination Jira Cloud site.

The digits in these quick reports serve as filters that allow you to refine your results in the Projects, Configuration, and Users tabs underneath.

For example, if you want to view all the workflows the deployment will add, just click on the + icon in the Workflows summary report. This will take you to the Configuration tab, where you can view information about each workflow the deployment will add to the destination.

Learn more about the information displayed in the Configuration tab for each configuration element.

Projects being deployed

The Projects tab shows you the projects that will be added to the destination Jira Cloud site and those in conflict with projects already present there.

The Projects tab here lists all the projects that will be added to or will modify projects on the destination Jira Cloud. In addition, we display the name, key, type, lead, and issue count of each project.

The Modification tag next to a project name indicates that the deployment will make changes coming from the project in the deployment scope to projects in the destination Jira Cloud. You can click on the project name to navigate to the project information on the current (source) Jira.

The Additon tag next to each project name indicates that the deployment will add the projects to the destination Jira Cloud. You can click on the project name to navigate to the project information on the current (source) Jira Cloud.

If there are conflicts between projects on the current Jira Cloud and the destination, you can use the Conflicts filter to navigate these errors.

Configuration elements being deployed

The Configuration tab lists all the configuration elements that will either be added, modified, or present errors on the destination Jira Cloud site. For each configuration element, we display its name, type, and problems if any, are detected.

In the Configuration tab, there is a tag for each configuration element name indicating its change type:

• Addition - the deployment will add the element to your destination Jira Cloud.

• Modification - an element from the current Jira will modify its matching element in the destination Jira Cloud.

The filters you can use here to find specific configuration changes rapidly are:

• Type - filters the elements based on their type.

• Addition - shows only the elements that will be added.

• Modification - shows only the elements that will be modified.

• Problems - shows the problems detected.

Users in the deployment

The Users tab shows the deployment status of all users from the deployed projects. The users can be either existing on the destination Jira Cloud site, new users that will be added to the cloud, or unknown users with undetermined statuses.

The users in a deployment can be:

• New: User who doesn’t have an account in the destination Jira Cloud site and will be invited to join.

• Existing: User with this email exists in the destination Jira Cloud site.

• Unknown: User doesn’t have a valid email address, and it cannot be determined if the account exists on the destination Jira Cloud site. The user either doesn’t have an email address or their email address is invalid.

Check out our complete Deploy Users tutorial, which introduces the different options you have to successfully manage your users during deployment and ultimately transfer them safely to the cloud.

View the detected problems

CMJ Cloud detects essential problems and conflicts in the configuration during the Analyze phase of deployment.

The detected problems are two types: warnings and errors. Warnings do not stop you from finishing your deployments, but errors do. So, in case the analysis detects any error or conflict between current Jira Cloud and destination Jira Cloud configurations, you need to take care of it and fix it before you can complete the deployment.

Open

Resolve the detected problems

In the Analyze phase of a deployment, you can resolve the detected conflicts without leaving the deployment wizard. To achieve that, CMJ Cloud allows you to:

• rename projects

• change project keys

• rename workflows and workflow schemes, issue type schemes, and

• rename project filters.

Learn more about transforming configuration elements during a deployment.

Rename and change key shortcuts to resolve conflicts

If CMJ Cloud detects a conflict while it scans source and destination configuration, it will offer shortcuts to resolve the problem. You’ll see them as a Rename or Change key (for projects) button in the conflict message in the Analyze Changes phase of the deployment. This way, you can fix conflicts faster, regardless of whether they’re between source and destination projects or configuration elements.

When there is a conflict in the configuration element name, you can use the Rename action suggested in the error message (check the image below). This action is available for projects and other configuration elements that can’t have duplicating names.

When there is a project key conflict, you can use the Change key action suggested in the error message (check the image below).