nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Announcement: Templates feature to be removed from Compass on December 1, 2025

Alastair Wilkes

What’s changing?

We’re deprecating and removing Templates in Compass, effective December 1, 2025. This change is part of our ongoing effort to focus on features that bring the most value to our customers.

This page explains:

What’s happening and when
How this affects you
What you need to do
Where to get help

What are Templates?

Templates in Compass are pre-configured components that help you quickly create new components, like services or repositories.

Key dates

Date	What’s happening	Details
September 9, 2025	Templates disabled for new customers	New tenants won’t be able to create or use templates.
December 1, 2025	Templates disabled for all customers	All tenants won't be able to create or use templates.
December 2025	Component conversion	All existing template components will be converted to the “Other” type.

Heads up: Starting November 1, 2025, you’ll see an in-product banner about this change.

What does this mean for your data?

After December 1, 2025, you won’t be able to create new components from templates.
Existing components of the “Template” type will be automatically converted to the “Other” component type.
Components that were created from a template aren’t affected; only the templates themselves.

Special cases to check

Custom fields

If you have custom fields that only apply to the “Template” type, those fields (and their data) will be deleted after migration unless you update them.
To keep this custom field data after migration, update your custom fields to also apply to the “Other” type, or migrate your templates to a different type that also has that custom field before December.

Scorecards

Scorecards that only apply to “Template” components will become manually applied after migration.
If a scorecard applies to multiple types (including “Template”), it will continue to apply to the other types after migration. You may need to update your filters.

Webhooks and parameters

Webhook URLs stored in templates will be deleted after migration; these were never surfaced after the template was created for security reasons.
Webhook parameters used in the create-from-template flow will also be deleted after migration, as they will serve no purpose.

What should I do next?

Review your existing templates and decide if you want to migrate them to a different component type.
Update any custom fields or scorecards as needed.

Need help?

We know this change may be disruptive, and we’re here to help. If you have questions or need support, please contact our support team.

Thank you for your understanding as we make this change. We appreciate your partnership.

Comments

Martin Alter

:-(

My hope was that the templates would have more focus and more functionality for automations, and more self-service.

Can you provide an overview of how to work with components?

Pete Stanley

Likewise keen to hear of any Atlassian offering in regards to self-service and automation solutions.

Georg Edlinger

it is really sad that templates will be removed.

Compass would lack its feature to be a real internal developer platform.

Self-service and automation seems to be less important in the Atlassian toolstack :-(

Andy Davies

Well that's a bad move. Templates could or rather should have been one of the core bits of functionality. Almost as bad is the lack of any reasoning as to why.

Ronny Katzenberger

You need to provide some sort of vision or recommendation. It's been a while since this has been announced and the deadline is approaching, yet there's no alternative provided.

Templates may not be the right approach as the developer journey entry point to begin with - so why don't you share your train of thought around this. You have unique knowledge about the industry and what your customers have been using successfully.

Not sharing this information puts all of us (customers) into discovery and ideation on something that should have been solve already.

Is there a shift towards CLI commands?

Luka Hummel - codefortynine

What's going to happen with Compass Components in Jira Software? It was nice to have Components synced across spaces.