Uploaded image for project: 'Migration Platform'
  1. Migration Platform
  2. MIG-1131

User created with admin username when an instance is subscribed

XMLWordPrintable

    • 143
    • Minor
    • 2

      Summary

      Note that this is mainly an issue when migration is involved.

      When a user subscribe to a new Atlassian Cloud instance, the user will be created in the instance under the username admin. When migrating the data from one instance to another, this would cause issues' ownership and its history to be transfered to another user who is the instance's creator in the target instance.

      During a Jira import, instance's creator(admin) is not replaced or altered.

      Steps to reproduce

      1. Subscribe to a new Atlassian Cloud instance - A.
      2. Create a project and a few issues.
      3. Subscribe to another instance using a different Atlassian account - B.
      4. Export from A.
      5. Import into B.
      6. Check the issues created in #2 for its reporter. The reporter has been changed to the user account which created B.

      Expected result

      Instance's creator username follows the username from email address.

      Actual result

      Instance's creator username is set to admin causing the tranferred ownership to be possible.

      Workaround

      Ensure that the instances' creator is the same Atlassian account user.

       

       

          Form Name

            [MIG-1131] User created with admin username when an instance is subscribed

            Dylan added a comment -

            Hi all,

            Thanks for watching - we've released a new backend synchronisation process between our identity service and the jira site imports that breaks the dependance on usernames. We're resolving this bug as Fixed as we've had no further reports in the last month. Please do reach out if you're still impacted and we can re-assess if needed.

            Cheers
            Dylan - Migrations Service Enablement

            Dylan added a comment - Hi all, Thanks for watching - we've released a new backend synchronisation process between our identity service and the jira site imports that breaks the dependance on usernames. We're resolving this bug as Fixed as we've had no further reports in the last month. Please do reach out if you're still impacted and we can re-assess if needed. Cheers Dylan - Migrations Service Enablement

            Somjit (Inactive) added a comment -

            No Dylan, we have not tested this.

            Somjit (Inactive) added a comment - No Dylan, we have not tested this.

              Unassigned Unassigned
              mfahd Fahd
              Affected customers:
              8 This affects my team
              Watchers:
              31 Start watching this issue

                Created:
                Updated:
                Resolved: