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