Skip to main content
A project template is the starting configuration for new projects. It bundles workflows, work item types, field collections, the views a project shows, the fields a project must fill in and an optional phase model. Projects created from it stay linked, so a change to the template reaches them. Who can do this?

System templates and your templates

System Settings → Content & Organization → Project Templates has two lists: Templates are available in every Space.

Create a template

Create the parts first: workflows, work item types and field collections. Then:
1

Start a template

Click New Template.
2

Fill in the editor

3

Save

Click Create Template.
4

Add project fields and phases (optional)

Open the template again with Edit Template. Two more sections appear, each with its own save button:
A new project gets everything the template carries in one step: its work item types, field collections, default workflow, views and features, and then its phases, quick filters and project home. If copying the phases, quick filters or home fails, the project is still created and you see a warning; add the missing part in the project settings. Members choose the template in the first step of New Project, under System Templates or Custom Templates, then enter Project Name and Project key in Project Details.

Linked projects and propagation

A project created from a template is linked to it. Its Settings → General shows Synced with template, and the sections Project features, Status, Work Item Types and Fields are read-only. Every time you save a template, Collabase aligns the linked projects in the background. The template page shows the state under Propagation to linked projects: Running, Up to date, Failed or Interrupted, how many projects follow the template and how many were aligned. Only one run per template is active at a time. If you save again while a run is going, the run continues with the new version. If a run is Interrupted or Failed, click Propagate again; projects that are already aligned are skipped. A project you detach during a run is left as it is.

Detach a project

Detach a project when its team needs its own configuration.
1

Open General

In the project, open Settings → General.
2

Detach

Click Detach and confirm with Detach Project. You see Project successfully detached from template.
Detaching cannot be undone. The project keeps its current configuration, including its work item types and the project fields the template asked for, and no longer receives template changes. The audit log records who detached the project.

Delete a template

Click Delete Template on a card and confirm. The dialog names how many projects still follow the template. Those projects are detached: they keep their work item types, field collections, features, workflow and the project fields the template asked for, and no longer receive template changes. No new project can use the template. This cannot be undone. System templates cannot be deleted.

Troubleshooting

Set up projects for a team

The order in which to build fields, types, workflows and templates.

Configuration model

Linked and detached projects compared.
Last modified on October 23, 2026