On this page:
|
Analysis of configuration changes to destination Jira Cloud
After CMJ Cloud finishes analyzing the project configurations in the deployment and the configuration elements associated with them, it presents a detailed report of the changes that will be introduced to the destination Jira Cloud site.
...
The sections below explain the information presented in the phase Analyze changes phase of the deployment.
...
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 to, modified on the destination Jira Cloud, or have problems.
The first section of the Analyze changes page contains quick reports for each configuration element type in the deployment, and each report shows:
how many elements of this type will be added to the destination Jira Cloud’s configuration,
how many elements of this type will be modified on the destination Jira Cloud’s configuration, and
the count of problems detected with configuration elements of a given type.
The numbers , or present errors on the destination Jira Cloud site.
The digits in these quick reports serve as filters, showing you the refined that allow you to refine your results in the 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. Then, in the Configuration This will take you to the Configuration tab, where you will 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 on the cloudalready 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
| Status | ||||
|---|---|---|---|---|
|
The Addition
| Status | ||||
|---|---|---|---|---|
|
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 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.
In the Configuration tab, there is a tag for each configuration element name indicating its change type:
...
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 tab on the Analyze changes phase contains all the information about the deployment status of your users.
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 its 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 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 Cloud and destination Jira Cloud configurations, you need to take care of it and fix it before you can complete the deployment.
| Infotip |
|---|
We advise you to carefully read through the texts of the problems and follow the resolution procedures if any are provided. |
...
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.
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 a deployment. Learn more about transforming configuration elements during a deployment.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).
...