The 

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

Configuration elements being

...

deployed

The Configuration tab shows you all configuration element changes that will be applied to Jira Cloud and if any problems are detected.The Configuration tab lists all the configuration elements that will either be added to or modified on your , 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.

When the Power Admin app is installed on your Jira Server/Data Center, there is a link in the Usage column. That link redirects you to a Power Admin page showing where and how the configuration element is used across the Jira Server/Data Center instance. Learn more about the Power Admin app

In the Configuration tab, there is a tag to 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 on 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 migrated 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 status.

You also have the powerful option to change how a user will be migrated. Users with changed deployment details are marked as customized.

The Users tab on the Analyze changes phase contains all the information about the deployment status of your users, plus the option to customize their user mapping. With the custom user mapping, you can map a source user to a different cloud account and resolve user errors like missing or invalid email addresses.

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 on this 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 its their email address is invalid.Customized: User is mapped to an account on the Jira Cloud site via custom mapping.

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

View the detected problems

CMJ Cloud deployment Tool detects essential problems and conflicts in the configuration during the Analyze phase of a 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’s Jira Cloud and destination Jira Cloud’s Cloud configurations, you need to take care of it and fix it before you can complete the deployment.

[change screenshot]

...

Resolve the detected problems

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

• rename projects

• change project name and keykeys

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

• rename project filters

...

• .

Learn more about transforming configuration elements during a deployment.

Rerun analysis when problems are detected

To create deployments to Jira Cloud sites:

...

Start a deployment as described in the deployments tutorial.

...

Review what will be added to and modified on the cloud on the Analyze step. If the deployment detects any problems or conflicts between the server and cloud projects, the analysis will alert you and show you the details of each problem.

...

On the Analyze changes step, review if any configuration problems are detected.

...

If you have configuration errors or conflicts, you need to resolve them before migrating. Otherwise, you won’t be able to proceed with the deployment.

...

Click the Rerun analysis button to check if you have successfully resolved the errors. The gif below illustrates how to rerun the analysis after fixing the detected errors. [change to screenshot]

...

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).

...