Details
-
Bug
-
Resolution: Timed out
-
Low
-
18
-
Minor
-
Description
Issue Summary
User content is mapped based on Username and not email address
Steps to Reproduce
- Create a user called admin2 on your server instance (lets say this user has email xyz_user@atlassian.com)
- Create some content with this user in the Server instance.
- Generate a backup on the server instance
- Have a user in Cloud with the username admin2 but with another email (lets say abc_user@atlassian.com)
- Perform a Jira site import on the site from the backup from Step 3.
- Choose the option to merge users.
Expected Results
User Content for user xyz_user@atlassian.com is mapped from Server to Cloud based on email address.
Actual Results
User Content for user xyz_user@atlassian.com is mapped from Server to Cloud based on username matching. So the content gets mapped to user with email abc_user@atlassian.com
Workaround
Content will be mapped correctly if the usernames match in the Jira Server and Cloud instances.
Attachments
Issue Links
- relates to
-
JSWCLOUD-19152 Incorrect externalId in AO_82B313_PERSON.ACCOUNT_ID
- Closed
-
MIG-1131 User created with admin username when an instance is subscribed
- Closed