Projects & issues
Issue templates
Start bugs, features and multi-part work from a template, with fields to fill in and sub-tasks made for you.
An issue template starts a new issue with its title, description, labels, priority, status and estimate already set, and can add sub-tasks with it. Templates ask for a few fields (the steps to reproduce a bug, say) and put your answers in the right places.
Using a template
On a board, choose + on a column and then From template… under the title box, or New issue from template in the board's … menu. Pick a template: the board's own come first, then the workspace's, each with a line about when to use it.
Fill in its fields. The ones marked with * are required: if one is empty, Deckbell says which and creates nothing. A preview shows the title and the sub-tasks as they'll be made. Choose Create issue, and the board says what was made, for example "Created WEB-12 with 4 sub-tasks."
- If the template sets a status, the issue starts there; otherwise it goes in the column you started from.
- If the template has sub-tasks, they're created with the issue, and those marked "blocked by the first" are linked as blocked by the first sub-task. If something can't be created, nothing is: you never end up with half the sub-tasks.
- If a template's label was archived, or its default assignee is no longer on the board, the issue is created without it and you see a note saying so.
Change anything else on the new issue as usual. Through the API or an AI assistant, you can also give values with the template:
- a description you give replaces the template's;
- labels you add go on top of the template's (if a label belongs to a group that allows one label per issue, yours replaces the template's);
- the priority, status, assignee and due date you give win over the template's.
The Android, iOS, macOS and Windows apps have From template… too.
Making templates
Board admins manage a board's templates in Board settings → Issue templates: New template, Edit, Archive and, from the Archived list, Restore. Everyone who can create issues on the board can use them. Editing or archiving a template doesn't change issues made from it.
Workspace templates
Workspace templates are offered on every board, after the board's own. Workspace owners and admins manage them in Workspace settings → Issue templates, the same way as a board's (or through the API or an AI assistant). Board settings lists them without changing them.
A workspace template's labels and status are names, such as
bug, risk-low and Todo. Each board uses the labels and status it has with
those names; ones it doesn't have are left out, with a note when the issue is
created.
A template has:
- a name (unique on the board) and a short note on when to use it;
- a title, which can include fields, e.g.
[Bug] {{title}}; - a description in Markdown with fields, e.g.
## Steps {{steps}}; - the fields that are required;
- default labels, priority, status and estimate;
- up to 20 sub-tasks, each with its own title, a default assignee, and whether it's blocked by the first sub-task.
A field is any name in double braces: {{steps}}, {{browser}}. What people
type is put in as it is: text that itself contains {{…}} is never filled in
again.
Examples
Bug
-
Title:
[Bug] {{title}} -
Description:
## Steps to reproduce {{steps}} ## Expected {{expected}} ## What happened {{actual}} ## Browser / app version {{environment}} -
Required: title, steps, expected, actual
-
Labels: bug. Priority: high. Status: Todo.
Feature
-
Title:
{{title}} -
Description:
## Problem {{problem}} ## Proposal {{proposal}} ## Done when {{done_when}} -
Required: title, problem
-
Labels: feature. Status: Backlog.
Cross-repo change
- Title:
{{feature}} - Description:
Ship {{feature}} in every app. Details: {{details}} - Required: feature
- Sub-tasks:
API: {{feature}}(label api)Web: {{feature}}(label web), blocked by the firstAndroid: {{feature}}, blocked by the firstiOS and macOS: {{feature}}, blocked by the first
With AI assistants and the API
Assistants connected through MCP can list a board's
templates and create issues from them. The API has the same:
GET /templates?project=WEB, and template / template_values on
POST /issues.