On this page:
Deploying users
With CMJ Cloud’s deployments, the users associated with the deployed configuration will be automatically included in the deployment. After creating a deployment, selecting projects to deploy, and reaching the Analyze changes phase, you’ll be able to review the users included.
Which users are deployed to the destination Jira Cloud?
Jira users, groups, and roles are integral to the project configuration - permissions, notifications, workflows, etc. Therefore, any users, groups, and roles used in the project you are attempting to deploy will be included in the deployment.
After adding projects to the deployment, users referenced by configuration elements associated with these projects are included. For example, users assigned to issues in a particular project, users assigned as project leads, or single users assigned to project permissions, will be included in the deployment.
How are source Jira Cloud users deployed?
Users who don’t have an account on the destination Jira Cloud site will be invited to join after the deployment.
Users with emails that exist on the destination Jira Cloud site won’t be deployed and are marked as existing.
Users who either don’t have an email address or have an invalid email address will be reported as a problem. These are inactive users that have been deleted or deactivated by a Jira administrator.
In these cases, the deployment can’t continue as CMJ Cloud won’t be able to determine if the user exists on the destination Jira Cloud site or not. Therefore, you first need to resolve these problems and then start the migration from the beginning.
User statuses during deployment
The users in the deployment are reported in the Analyze changes > Users tab. There are four user statuses you can observe in the Users tab:
NEW User doesn’t have an account on the destination Jira Cloud site and will be invited to join.
EXISTING User with this email exists on 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 email address is invalid.
