...
Users are never deleted or changed if they exist, and user passwords are not exported in a configuration snapshot.
When creating a snapshot, users will only be exported if they are referenced by the exported configuration objects or issue data.
When the user is created on deployment of the configuration snapshot, the system will generate a new password for the created user. This password cannot be accessed or viewed and can only be reset by the user through the Can’t access your account? button on the target Jira instance.
If a user must be added when deploying a configuration snapshot, the user will be added in to the default directory (i.e., the first directory with Create user permissions). Note that a warning is also logged in the Audit Log. If the option "Do not merge changes to During a snapshot deployment, if the "Project Roles" is selected and the user is referred only by a project role, then the user addition will be skipped during the deploymentoption is unchecked, CMJ will skip adding any users used in a project configuration or mentioned in the project’s issues. In this case, the Project lead will still be added.
Groups
Groups are never deleted or changed if they exist.
When creating a configuration snapshot, groups will only be exported if they are referenced by the exported configuration objects. Note the exported group will be empty.
If a group must be added when deploying a configuration snapshot, the group will be added as an empty group - it is up to the user to configure the group. Note a warning is also logged in the Audit Log.
...
There is support for conditions, validators, and post-functions defined in a standard Jira, plus the one specified in the Supported Apps. Workflow extensions defined in other plugins may not load correctly.
...