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