Hi everyone, Carol here with some good news for anyone who’s been asking for custom templates beyond Enterprise.
Custom templates for team-managed spaces are now available on Jira Standard and Premium.
That means admins and team leads on Standard and Premium can turn a well-run team-managed project into a reusable blueprint, then spin up the next one in seconds: same structure, same workflows, same views. No more rebuilding from a blank slate every time a recurring initiative kicks off.
Previously this was limited to Enterprise. We’re expanding access so more teams can standardise the good stuff without waiting on a central queue for every new space.
What you can do
- Save a custom template from a team-managed space that’s already working well
- Share it across your site or with trusted team members so other teams can pick it from the template gallery
- Launch ready-to-work projects with pre-configured issue types, workflows, views, and more
- Add rich context (descriptions, guidance, branding) so people know which template to choose
Note: Company-managed custom templates remain an Enterprise capability.
Pair it with Space Policies for guided autonomy
Templates help you scale how teams start work. Space Policies help you scale within org standards.
With Space Policies, Jira admins can set lightweight guardrails on team-managed projects so teams reuse global fields and/or global statuses, instead of inventing local ones that fragment reporting. You get three ready-to-use options:
- Global fields only
- Global statuses only
- Global fields and statuses
You can also set a site default for new team-managed spaces, and attach a policy to the project behind a custom template so every space created from that template inherits the right guardrails automatically.
In other words: teams still move fast and self-serve. Admins still protect consistency for reporting and shared language. Those are not opposing goals anymore.
Read more here: Jira Space Policies: give teams autonomy within admin guardrails
Why this matters
This is a guided autonomy story in practice:
- Publish the pattern with a custom template
- Set the boundaries with a Space Policy (global fields and/or statuses)
- Let teams launch without starting from scratch or opening a ticket for every new project
Faster kickoff for teams. Cleaner standards for admins. Better reuse of the setups that already work.
How to try it
- Open a team-managed space you’d happily reuse
- (Optional) Apply a Space Policy so new projects from that template stay on global fields/statuses
- Save it as a custom template
- Create your next space from the template gallery
Learn more
I’d love to hear how you’re planning to use this. What templates are you creating first, and are you pairing them with Space Policies?
Thanks,
Carol
