Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-79432

Using non-destructive site import maps user content based on username and not email.

XMLWordPrintable

      Issue Summary

      User content is mapped based on Username and not email address

      Steps to Reproduce

      1. Create a user called admin2 on your server instance (lets say this user has email xyz_user@atlassian.com)
      2. Create some content with this user in the Server instance.
      3. Generate a backup on the server instance
      4. Have a user in Cloud with the username admin2 but with another email (lets say abc_user@atlassian.com)
      5. Perform a Jira site import on the site from the backup from Step 3.
      6. 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.

          Form Name

            [JRACLOUD-79432] Using non-destructive site import maps user content based on username and not email.

            Matthew Hunter added a comment -
            Atlassian Update - July 19, 2022

            Hi everyone,

            Thank you for previously raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.

            As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.

            Thank you again for providing valuable feedback to our team!
            Jira Cloud team

            Matthew Hunter added a comment - Atlassian Update - July 19, 2022 Hi everyone, Thank you for previously raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users. As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know. Thank you again for providing valuable feedback to our team! Jira Cloud team

              Unassigned Unassigned
              vgambhir Vik
              Affected customers:
              1 This affects my team
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: