Team-managed spaces have always had one very attractive promise:
“Let the team manage Jira without needing a Jira admin for everything.”
Great idea.
Until you open the admin area six months later and discover:
- 14 versions of “In Progress”
- three fields called “Business Priority”
- two fields called “Priority Business”
- another one called “Business Priority New”
- and nobody remembers who created any of them.
Welcome to autonomy. 😄
This is one of the reasons I’ve always had mixed feelings about team-managed spaces in larger Jira environments.
They are incredibly useful for giving teams independence.
But independence without some governance can quickly turn into configuration fragmentation.
And that is exactly why I think Space Policies + Global Statuses are one of the more interesting Jira admin changes in 2026.
The original team-managed idea was good
The concept behind team-managed spaces makes sense.
Instead of asking a Jira admin for every small configuration change, teams can manage things themselves.
They can configure:
- workflows;
- statuses;
- fields;
- views;
- access;
- work types.
And changes remain isolated to that space.
For smaller organizations or independent teams, this can work extremely well.
The problem usually appears when the number of spaces starts growing.
One team creates:
Customer
Another creates:
Customer Name
Another:
Client
And another:
Client Name
Technically, all four teams got what they needed.
From a governance perspective…
well, now we have four fields representing almost the same concept.
The reporting problem comes later
The funny part is that configuration fragmentation usually doesn’t hurt immediately.
The team creates its space.
Everything works.
Everyone is happy.
Then somebody from management asks:
“Can we create one dashboard showing this information across all teams?”
And that is when the Jira admin starts discovering archaeology.
Different fields.
Different statuses.
Different workflows.
Different naming conventions.
Different interpretations of what “Done” actually means.
The team-managed flexibility that helped teams move quickly now makes cross-space reporting much harder.
Atlassian itself uses a very similar status example: multiple teams creating variations such as “In Progress”, “Progress”, “In-Progress” and “Working”, which then makes JQL and reporting inconsistent.
Enter Space Policies
Space Policies try to solve this without completely removing team autonomy.
And I think that distinction is important.
The idea is not:
“Admins control everything again.”
Instead, it is:
“Teams can still manage their spaces, but inside some basic guardrails.”
Today, Jira provides three policy options:
- Global fields only
- Global statuses only
- Global fields and statuses
When a policy is applied, teams can continue using the global configuration available on the Jira site, but they can no longer create new local fields or statuses covered by that policy.
That is a pretty significant change.
Global Statuses: probably my favorite part
For me, statuses are one of the easiest places for Jira configuration to become unnecessarily fragmented.
Imagine three teams:
Team A
To Do → In Progress → Done
Team B
Backlog → Working → Completed
Team C
Open → Doing → Finished
From each team's perspective, this is perfectly logical.
From the Jira admin's perspective:
Why do we have three names for the same lifecycle?
With Global Statuses, team-managed spaces can reuse approved statuses that already exist across the site.
The teams can still design their own workflow.
They just reuse a common vocabulary.
That is the important part.
You are not necessarily forcing every team to use the exact same workflow.
You are making sure everyone speaks roughly the same Jira language.
Autonomy vs governance was always the real problem
Historically, admins had two uncomfortable options.
Option 1
Allow teams to create their own configuration.
Result:
Maximum flexibility. Potential chaos.
Option 2
Restrict team-managed spaces heavily.
Result:
Every change becomes:
“Hi Jira Admin, can you create this field?”
Then five minutes later:
“Actually, can you rename it?”
Then:
“Can you add another option?”
Congratulations.
You are now the Jira configuration help desk.
Space Policies create an interesting middle ground.
Atlassian describes this as giving teams autonomy while admins define the guardrails once.
And I think that is exactly the right way to describe it.
The policy I would probably use
If I were designing governance for a larger Jira Cloud instance, I would seriously consider:
Global fields + Global statuses
for most new team-managed spaces.
Why?
Because fields and statuses are two of the configuration areas that most directly affect:
- JQL
- dashboards
- reporting
- automation
- integrations
- administration
If every team creates its own versions of these objects, everything downstream becomes harder.
I would still let teams control things such as:
- workflow structure;
- boards;
- views;
- work organization;
- local ways of working.
That gives them flexibility without letting the site configuration grow indefinitely.
Another interesting part: make it the default
You can also define a Space Policy as the default policy for new team-managed spaces.
That means you don’t need to remember:
“Oh, someone created another space. Let me apply the policy.”
New spaces can receive the guardrails automatically.
This sounds small.
But anyone managing a large Jira site knows that configuration you need to remember manually will eventually be forgotten.
Usually on a Friday afternoon.
Custom templates make this even more interesting
The other piece that makes this feature stronger is the combination with custom templates.
You can create a team-managed space that already represents a good configuration, turn it into a reusable template, and associate a Space Policy with it.
New teams can then start with:
A known configuration + governance rules already applied.
Atlassian describes the combination as:
Templates define how teams start.
Space Policies define the boundaries they operate within.
That combination makes a lot of sense to me.
Instead of Jira admins building every space manually:
Create a good model once → turn it into a template → apply governance → let teams self-service.
That scales much better.
But what about existing spaces?
This is where things get a little more interesting.
If you apply a policy to an existing team-managed space that already contains local fields or statuses, Jira does not simply delete them.
Existing configuration continues working.
Instead, Jira identifies policy conflicts that admins can review and resolve over time.
I think this is the right behavior.
Imagine enabling a policy and Jira immediately saying:
“Great! I deleted 37 fields and broke your workflow.”
Nobody wants that feature.
The conflict model gives admins a migration path instead.
This also means governance is not magically fixed
Space Policies are useful.
But enabling one does not suddenly clean five years of Jira configuration.
If your instance already has hundreds of duplicated fields and statuses, you still need to decide:
- which global field should become the standard;
- which statuses should remain;
- which automations reference local configuration;
- which filters need updating;
- which workflows need adjustment.
Atlassian specifically provides guidance for updating automations, workflows, filters and boards after moving configuration toward a Space Policy.
So I would see Space Policies as:
a way to stop creating new chaos
before dealing with the existing chaos.
And honestly, that is already a pretty good start.
One thing I would not do
I would not create a gigantic library of global fields just because teams can no longer create local ones.
Otherwise we simply move the problem.
Instead of:
500 local fields
we end up with:
500 global fields
Same mess.
Different menu.
Governance still requires someone to decide:
Do we already have something that represents this business concept?
The feature gives us guardrails.
It does not replace good administration.
My ideal model
If I were designing a new Jira Cloud governance model today, I would probably think about it like this:
Global level
Define the important shared concepts:
- common statuses;
- common business fields;
- naming conventions;
- reporting requirements.
Templates
Provide good starting configurations for different teams.
Space Policies
Prevent unnecessary duplication of fields and statuses.
Teams
Let teams customize their actual working process inside those boundaries.
To me, that is much healthier than choosing between:
complete centralization
and
complete freedom.
Final thoughts
I don’t think team-managed spaces were ever the problem.
The problem was scaling them.
Giving five teams autonomy is easy.
Giving 200 teams autonomy while still expecting consistent reporting is a very different challenge.
Space Policies and Global Statuses feel like Atlassian acknowledging that reality.
Teams still get flexibility.
Admins get guardrails.
And hopefully we get fewer statuses called:
In Progress Final New 2
That alone might be worth enabling the beta. 😄
Space Policies are currently in open beta and available for team-managed spaces on Jira Standard, Premium and Enterprise, so I would still test the behavior carefully before treating it as a finished governance model.
I’m curious how other Jira admins see this:
Would Space Policies make you more comfortable allowing teams to create and manage their own spaces?
Or do you still prefer company-managed spaces when governance really matters?