Changes to Teams, and their impacts on open sites

[#1]

In the coming months, we’ll be unifying the Shared Teams that are used in Advanced Roadmaps with Atlassian Teams - the teams that are used in the People dropdown in many of our products today. These teams will replace existing shared teams in Advanced Roadmaps with no loss in functionality or related capabilities.

As part of the migration, teams in Advanced Roadmaps will change from being a site-wide entity to a global one that can be used and viewed across your organization’s other Atlassian Sites. To protect sensitive team data (e.g. - team names), users viewing an open Jira site will only be able to see organization-wide teams if they also have access to a closed site in the same org. Users who can only access open sites won’t be able to see teams or assign issues to a team; they'll only be able to see and assign issues to plan-only teams. 

We recognize the impact this will have on some organizations so please let us know if this impacts you in the survey form below. These changes to Team visibility are required to maintain data privacy for our customers. A possible workaround for customers affected by this is to use plan-only teams in Advanced Roadmaps on open sites.

We value opportunities to better understand how customers on open sites use Advanced Roadmaps. Please comment on this post, or complete the survey below to share your experience with us: https://forms.gle/Fn48kjjE84JEzLEi6

[Dave Mathijs]

Curious about how the TEAM aspect in Atlassian products will evolve and become much easier to manage as there are way too many Team fields right now, each with a different function.

[Jimi Wikman]

Interesting. Where will data be stored for global teams, and how will that work with GDPR? Will global team data reside in Europe by choice, or is it like other global data stored outside?

Just so I understand this change properly...

• Plan Based Teams will still be Plan Based Teams.
• Shared Teams will become global teams, just like People teams are now.
  • If your Jira site is open then
    • If the user is registered, but don't have access to a closed site (any site? Like confluence or JSM?) then they can't see teams.
    • If the user is anonymous, then they can't see teams.
  • If your Jira is closed, then anyone with access to the closed site can see all teams.

If we want to avoid exposing teams, or if there are GDPR issues, then every plan must create the same team in every plan as plan-only teams?

There is no way to restrict access to who can see these teams, globally and in Jira itself? Maybe that will come later than perhaps?

I think this could cause a lot of issues, or almost none, depending on how the GDPR question is handled and how many companies that will not want to have their team compositions exposed...

[Erin Quick-Laughlin]

"These teams will replace existing shared teams in Advanced Roadmaps with no loss in functionality or related capabilities."

1. So, if we have existing Shared Teams, with capacities and people and other AR-based settings, they are converted to Global teams, and keep all settings and people associated?
2. How do we reference these teams in JQL going forward?  Currently, we reference a Shared Team by "Team[Team] = 123".  
   1. Does this change to a different variable name than Team[Team]?
   2. Do we keep the same IDs, or do we have to update filters to replace them with new IDs, or perhaps alphabetic names?

Thanks ahead!

[Aaron Mosny]

@Rhys Christian can you turn on this feature for our Jira instance?

[Yerbol Nisanbayev]

Hey @Dave Mathijs , thank you for the interest, that's exactly right and it is a problem we are looking to address. There will be a few more announcements throughout the year on consolidating teams and making them a more integrated part of your workflow. 

[Christine Corona]

@Rhys Christian can any user create Atlassian Teams or is there a permission that administrators can configure so only specific groups (or none at all outside of admins) can create a team?

Thank you