Uploaded image for project: 'Atlas'
  1. Atlas
  2. ATLAS-96

Multiple JCMA migrations on the same Cloud site will result in duplicate teams

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • People and Teams
    • None
    • 66

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Issue Summary

      Running multiple migrations using JCMA can result in duplicate teams listed for every site within the same organization (production, sandbox, etc)

      Steps to Reproduce

      1. Create a sandbox site
      2. Create Advanced Roadmap Plans, Teams, etc
      3. Use JCMA to migrate some projects
        • Use the option to migrate Advanced Roadmaps
      4. Delete the sandbox site and recreate a new sandbox
      5. Repeat the JCMA migration

      Expected Results

      • As the Site is being deleted, the user expects that all Jira data being migrated is erased

      Actual Results

      • Teams are not stored at the site level. They are at the organization level. During each migration, the teams are added as duplicates. Therefore, other sites within the same org will also see the duplicate teams

      Workaround

      Due to the following feature request: JRACLOUD-82782: Ability to Retrieve all Teams via Rest API for Bulk Action there isn't an easy way for admins to handle duplicates. They must try and collect the Team IDs in order to script a solution to delete the duplicate teams.

      Suggestion:

      • A user should be able to easily audit their teams and perform bulk actions.
      • Public KBs should give more details about Teams and how they are associated to Org and Sites

            [ATLAS-96] Multiple JCMA migrations on the same Cloud site will result in duplicate teams

            Valentina Blagoev made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 991228 ]
            Sam Göksün made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 962961 ]
            Andrew T made changes -
            Link New: This issue relates to JRACLOUD-82782 [ JRACLOUD-82782 ]
            Bharath K V made changes -
            Component/s Original: Jira - Migration Assistant - AR Migrations [ 66438 ]
            Component/s New: People and Teams [ 72714 ]
            Key Original: MIG-2012 New: ATLAS-96
            Support reference count Original: 12
            Project Original: Migration Platform [ 19710 ] New: Atlas [ 22510 ]
            SET Analytics Bot made changes -
            Support reference count Original: 11 New: 12
            Bharath K V made changes -
            Description Original: h3. Issue Summary
            Running multiple migrations using JCMA can result in duplicate teams listed for every site within the same organization (production, sandbox, etc)

            h3. Steps to Reproduce
            # Create a sandbox site
            # Create Advanced Roadmap Plans, Teams, etc
            # Use JCMA to migrate some projects
            ** Use the option to migrate Advanced Roadmaps
            # Delete the sandbox site and recreate a new sandbox
            # Repeat the JCMA migration


            h3. Expected Results

            * As the Site is being deleted, the user expects that all Jira data being migrated is erased

            h3. Actual Results

            * Teams are not stored at the site level. They are at the organization level. During each migration, the teams are added as duplicates. Therefore, other sites within the same org will also see the duplicate teams

            h3. Workaround

            Due to the following feature request: [JRACLOUD\-82782: Ability to Retrieve all Teams via Rest API for Bulk Action|https://jira.atlassian.com/browse/JRACLOUD-82782] there isn't an easy way for admins to handle duplicates. They must try and collect the Team IDs in order to script a solution to delete the duplicate teams.

            Suggestion:
            * JCMA should improve the handling of the scenario to prevent duplicate teams.
            * A user should be able to easily audit their teams and perform bulk actions.
            * Public KBs should give more details about Teams and how they are associated to Org and Sites             		New: h3. Issue Summary

            Running multiple migrations using JCMA can result in duplicate teams listed for every site within the same organization (production, sandbox, etc)
            h3. Steps to Reproduce
             # Create a sandbox site
             # Create Advanced Roadmap Plans, Teams, etc
             # Use JCMA to migrate some projects
             ** Use the option to migrate Advanced Roadmaps
             # Delete the sandbox site and recreate a new sandbox
             # Repeat the JCMA migration

            h3. Expected Results
             * As the Site is being deleted, the user expects that all Jira data being migrated is erased

            h3. Actual Results
             * Teams are not stored at the site level. They are at the organization level. During each migration, the teams are added as duplicates. Therefore, other sites within the same org will also see the duplicate teams

            h3. Workaround

            Due to the following feature request: [JRACLOUD-82782: Ability to Retrieve all Teams via Rest API for Bulk Action|https://jira.atlassian.com/browse/JRACLOUD-82782] there isn't an easy way for admins to handle duplicates. They must try and collect the Team IDs in order to script a solution to delete the duplicate teams.
            h3. Suggestion:
             * A user should be able to easily audit their teams and perform bulk actions.
             * Public KBs should give more details about Teams and how they are associated to Org and Sites
            Marcin Kempa made changes -
            Due Date Original: 07/Nov/2024
            Bharath K V made changes -
            Affects Version/s Original: JCMA - 1.11.7 [ 108502 ]
            Was this caused by a recent change? Original: No [ 19032 ]
            Workflow Original: JAC Bug Workflow v3 [ 4483374 ] New: JAC Suggestion Workflow 3 [ 4491020 ]
            Issue Type Original: Bug [ 1 ] New: Suggestion [ 10000 ]
            Priority Original: High [ 2 ]
            Status Original: Gathering Impact [ 12072 ] New: Gathering Interest [ 11772 ]
            SET Analytics Bot made changes -
            UIS Original: 57 New: 66
            SET Analytics Bot made changes -
            Support reference count Original: 10 New: 11

              Unassigned Unassigned
              asalinasii@atlassian.com Alfonso S.
              Votes:
              4 Vote for this issue
              Watchers:
              18 Start watching this issue

                Created:
                Updated: