Issue templates

Templates speed up issue creation and apply properties without adding each one by hand.

Issue template

OverviewCopy Anchor Link

An issue template pre-fills title, short description, the description document, and properties — type, status, priority, team, project, milestone, assignee, labels, and estimate.

A standard template fills the composer and leaves everything editable. A form template asks ordered questions first, then builds the issue from the answers.

When a team names a default template, new issues in that team start from it unless you change it. Personal issues have no team, so no template applies.

See Templates for project, request, and document templates.

Create standard issue templatesCopy Anchor Link

Create templates at Settings → Issues → Templates for the workspace, or Settings → Your teams → <team> → Templates for one team. Team managers author team templates; workspace templates need a workspace manager.

To create a standard template:

1. Click New template and choose Standard
2. Give it a name and, optionally, a description of when to use it
3. Set Visibility to the workspace or one team
4. Fill in starting properties. Leave the title empty to make the creator write one
5. Save

Standard templates cannot set a due date — ask for one as a form question instead. They do not create sub-issues.

Open the … menu on a template row for Edit, Duplicate…, Copy URL to create issue from template, or Delete. Deleting stops the template from being offered; issues already created from it are unchanged.

Workspace TemplatesCopy Anchor Link

Workspace templates are available when creating an issue in any team.

Team TemplatesCopy Anchor Link

Team templates are offered only in that team and can carry team statuses and labels. Sub-teams do not inherit a parent team's templates.

Create form templatesCopy Anchor Link

Form templates are more structured when certain information must be provided at creation.

To create a form template:

1. Click New template and choose Custom Form
2. Add questions under Form fields. Each has a type, Question, optional Field description, Identifier, and Required
3. Reorder questions by dragging, or with Alt and the arrow keys
4. Set default properties below the questions
5. Save

Generic form fieldsCopy Anchor Link

Question types: Text, Long text, Dropdown, Checkboxes, Date, Upload file, and Instructions.

Answers to non-property questions are written into the issue's main document in question order. Instructions text is copied in too.

Property form fieldsCopy Anchor Link

Property questions can ask for Title, Description, Type, Priority, Due date, Labels, Team, Assignee, Project, Milestone, and Estimate.

Default propertiesCopy Anchor Link

Set default properties below the questions so the created issue starts with those values even when the form does not ask for them.

Use issue templatesCopy Anchor Link

• Open the Template picker in the issue composer, beside the team
• Choose Create new issue from template… in the command menu (Cmd/Ctrl K)
• Open a link copied with Copy URL to create issue from template

If you already typed a value the template also sets, Pulse asks which to keep.

Default templatesCopy Anchor Link

A team can name the template the composer opens with. On Settings → Your teams → <team> → Templates, set Issues created by team members and Issues created by non-team members. A form template can only be the default for non-members.

Request templates live under Settings → Features → Customer requests, then Templates.

FAQCopy Anchor Link