FAQs and common migration challenges

What if I don’t assign a Team to a site during migration?

If you don’t choose a site for a Team before the migration deadline, we’ll automatically assign it to the site we think fits best, explained under ‘suggested site’ here. Don’t worry - you’ll have a one-month grace period after migration to review and change these assignments if needed. If you are not an org admin and want a Team moved to a different site, please ask your org admin for help.

My Team was assigned to the wrong site. How do I fix it?

• If you are an org admin: You can update a Team’s site assignment any time during the migration window and for one month after. Just use the team assignment screen in Atlassian Administration to make the change.

• If you are not an org admin: Reach out to your org admin and they can update the Team’s site for you.

What happens to the Team once it’s assigned to a different site?

Today, your Teams are visible to the entire organization. This means that a Team may be connected to a Jira work item in site X as well as a Jira work item in site Y.

If you decide to assign the Team to site Y, it will only be visible to users in site Y. This is what happens to the references of the Team in site X, where this Team is no longer visible.

Can I use the same Team in more than one site?

If you want a Team to be available in multiple sites, just make a copy of that Team in each site where you need it. Then, update any work or references to point to the right Team in each site. This way, your Teams stay connected and easy to find, no matter which site you’re working in.

Follow the steps documented here - we’ve applied it to sandbox sites in that example, but it is the same if you want to copy Teams over to any amount of sites.

Help and resources

• Join our community group to connect with others and ask questions.

• If you need further assistance, you can also contact support here.