How to map users while migrating projects from One instance to other instance ( both -Data center)

[IYTHA RAJESH]

Hi Community,

Recently I have migrated project by using configuration manager for Jira from one instance (Data center) to other instance (Data center). Issues along with attachments migrated successfully but users have not been mapped correctly as per the Target instance.

Here the source instance has different user name and target instance has different user name but the email ID for both instances are same. Before migrating the project we have added users into Target instance from Azure.

All the issues were mapped as per the source instance user names instead of target instance user names. Due to this users are unable to access the tickets/filters/boards.

Is there any way to map the users as per the Target instance while doing the migration or after. Please suggest.

Thanks,

Rajesh.

[Marc - Devoteam]

Hi @IYTHA RAJESH 

Hi  

If I quickly go over the documentation, there are limitations.

"User Management Normalization

Jira users, groups, and roles are an integral part of the Project Configuration - permissions, notifications, workflows, etc. Any users, groups, and roles used in the project that you are attempting to move will be included in the project snapshot, and during deployment, Configuration Manager will attempt to create them on the target server*. This will work for most cases but might have the following limitations:

• User with id johnsmith from the Source might already exist on the Target with a different id - john.smith or jsmith, for example. In this case, Configuration Manager will create a new user with id johnsmith, which won't be accurate.
• The user with id johnsmith from the Source and the user with the same id on the Target might be a different actual user. In this case, Configuration Manager will NOT create a new user with id johnsmith, which won't be accurate.
• The users will be created and will increase the user count, which might have license implications.
• The users/group creation might not be successful - due to the lack of a writable directory.

As of version 4.1.1 and later Configuration Manager has the option to exclude changes in Roles on deployment, which means that users and groups referred to only by roles will not be created on the target server. "

You might need to look into this.

Otherwise contact the vendor, on you issue, as this is related to their app