Templates

Template health

What the Healthy, Needs review and Broken badges mean, which configuration changes repair a template automatically and which only flag it, and the limits a template must stay inside.

A template references your organization's configuration — work types, custom fields, priorities, tags, boards, users, and teams. Those things change. Template health is how DevStride tells you when a change has left a template unable to do its job, instead of letting it quietly create the wrong work.

The badge

Health is checked every time a template is read, against your live configuration. There are three states:

BadgeMeaning
Healthy (green)Everything it references still exists and is usable.
Needs review (yellow)It holds values your organization no longer allows, such as a member who left, an archived team, or a tag taken off the item type. It can still be applied: you choose to fix it first, or to apply it and skip those values.
Broken (red)It has a problem that skipping can't fix, such as an item type that was removed or archived. It can't be applied until someone fixes it in the builder.

Hover the badge for the full list of reasons. When a template is broken, the reasons that block it are listed first.

A Needs review template can be picked in the Apply Template dialog. The preview lists each value that no longer fits and offers Fix the template or Apply and skip missing values. See Values that no longer fit.

An automation's Apply Template action applies a Needs review template too, skipping those values on every run and naming them in the run's history. See Apply a template to new requests.

A Broken template can't be picked. The picker names the problem. If you can edit the template, it offers Fix the template; otherwise it tells you to ask the owner or an admin. The server refuses it too, so a stale browser tab can't slip one through.

What happens when configuration changes

DevStride reacts differently depending on whether the change can be undone.

Irreversible changes repair the template automatically

When something is deleted outright, there is nothing to restore, so the reference is removed from the template and the owner is notified. The template stays applicable; it just no longer sets that value.

This happens when:

  • A custom field is deleted.
  • An option is removed from a custom field.
  • A tag is removed from its collection.
  • A priority is removed from its collection.

The owner gets a notification naming exactly what changed, and the affected node in the builder shows a dismissible note.

Reversible changes only flag it

When something is archived or deactivated it can come back, so DevStride changes nothing in the template and only flags it. Restore the referent and the template heals itself.

These changes make a template Needs review, so it can still be applied by skipping the value:

  • A team is archived.
  • A member is deactivated.
  • A persona is retired.
  • A board or board folder is archived. This affects board and cycle placement, and the item is then created off that board.

This change makes a template Broken:

  • A work type is archived.

The fix is either to restore the thing that was archived, or to edit the template to stop referencing it.

Deleted boards are flagged, not repaired

A board or board folder that is permanently deleted is also only flagged, even though it can't come back: the note on the node reads "Board "X" was permanently deleted. Choose another board for this template." Nothing is removed from the template, because a node with no board placement would silently create off-board work. Pick a different board (or None) in the builder.

Checking before you delete something

When you delete a custom field, tag, or priority, DevStride first tells you how many templates use it and what will happen to them — whether they'll be repaired or flagged.

A template that an automation's Apply Template action uses cannot be deleted; the message names the automation, so you can change or remove that action first.

Templates you don't have access to are counted but redacted: you'll see that N private templates belonging to other members are included, without their names or owners. The count is honest even when the details aren't yours to see.

Problems while you're building

The builder shows a problems count covering everything that would block an apply: broken references, fields that ask for a variable that isn't set, and blocking findings from the dry run. Non-blocking notes are deliberately kept off that counter and shown on the field they concern instead — a permanent warning badge on a perfectly good template just teaches people to ignore it.

Limits

A template must stay inside these bounds:

LimitValue
Nodes500 — workstreams, work items, and sub-items combined
Depth10 levels — sub-items don't count as a level
Variables20
Title length500 characters, after variables are filled in
Options per Options variable2 to 50
Template name100 characters
Template description500 characters

The variable cap is enforced as you build — the add control switches off at 20. Node count, depth, and title length are only checked when you save, so a very large template can be built and then refused. If that happens, the exact reason appears in a red banner above the builder.

Common problems

"This template cannot be applied inside a workstream" / "...inside a Story" — the template's root doesn't fit the target. Check the Applies to chips and see where a template can go.

A title shows {{SomeName}} literally after applying — that was a description, not a title. Unknown tokens in descriptions are left verbatim by design; in titles they're a blocking error. Check the variable name matches exactly.

The assignee didn't come through — the node also sets a team, and the assignee wasn't on it. An assignee outside the node's team is dropped when the item is created.

A variable type won't insert into a title — User, Team, and Board variables resolve to records rather than text. Only Text, Number, Date, and Options can be interpolated.

The apply stopped partway — an apply isn't a transaction. The failed node and its descendants are skipped, siblings still complete, and created work is kept. Use Copy error details to get the list of what failed.