Migration state for centralized user management customers
Get context surrounding how this will impact Teams features in your organization
Existing Team features (Teams in Jira, Team profiles, search, etc.) will continue to function as expected - being limited to a single site. However, while we support this configuration, you will encounter limitations with new Teams features.
Any team configuration will be shared across all your sites. Custom fields and team types will be shared across sites with their names potentially visible to end users. If this isolation is for data privacy reasons, please be careful with what values you put in those fields.
Understand the next steps for your organization to move out of this hybrid state
Most Atlassian customers have already aligned their Team visibility with their user management state. Our long term goal is to move your organisation to this state as well, so that all configuration and administration is in the same scope. This will simplify your overhead, while also enabling new features to be built more quickly.
In this hybrid state, your options are:
Move teams to global scope: If the reason you requested site-scoped teams is no longer valid we can make your teams no longer scope to a single site, visible across all of your sites. Please contact Atlassian Support to begin this process.
Maintain the hybrid migration state: You can remain in this state until Units becomes generally available. Units will allow you to define custom visibility boundaries (single site, multiple sites, or entire org). Public roadmap link with more details on Units.
Was this helpful?