Skip to main content

Applying templates automatically

A checklist appears on a work item when an active template matches the current context. You do not manually attach a template each time; the extension loads every matching template automatically.

This page focuses only on matching behavior. For the full process, field, and template setup, see Setting up checklists for work items.

Work item type​

Each template lists which work item types it applies to, for example Bug, User Story, or Task. A template is only considered if:

  • The current work item type is included on the template.
  • The template has a content field mapping for that same work item type.

If the mapping is missing, the template does not apply even if the work item type is selected.

The template editor is where you choose supported work item types and map the checklist field for each one:

Template editor showing work item types and field mappings

Team scoping​

Templates can be limited to specific teams using Available teams. If no restriction is set, the template is available to all teams in scope for the project.

When a work item is associated with a team, filtering helps ensure users see the checklists meant for their team’s process.

Project scoping​

Templates can be limited to certain projects with Visible in projects. If unset, the template is visible in every project where the rest of the rules match.

Together, work item type, team, and project determine which templates contribute checklists when you open a work item.

Template editor with Available teams and Visible in projects settings visible for one template.

Multiple matches​

More than one template can match the same work item. When that happens, the work item form shows multiple independent checklists, one per matching template.

How content is merged​

When the work item form loads, the extension renders checklists from matching templates and reads the existing markdown from each mapped content field.

If the field already contains checklist data, the extension merges the template structure with the stored markdown so that:

  • Existing completion state is preserved.
  • Skipped items stay skipped.
  • Existing custom items stay attached to that checklist.

This lets teams update templates without wiping out work already tracked on the work item.

For more on day-to-day use, see Working with checklists and Working with templates.