Work Item Templates
When your team creates the same kinds of work items repeatedly — bug reports, feature requests, onboarding checklists, release tasks — templates eliminate the repetitive setup. A template defines a reusable pattern of fields (title, description, priority, labels, assignees, and more) that can be applied when creating a new work item, giving you a consistent starting point every time.
Create a template from an existing work item
The fastest way to build a template is to base it on a work item that already has the structure you want:
- Open the work item you want to use as a base.
- Click the three-dot menu in the work item header.
- Select Save as Template.
- A dialog opens showing the fields that will be included in the template.
- Give the template a name (e.g., "Bug Report", "Feature Request").
- Optionally add a description for the template to help teammates understand when to use it.
- Review the pre-filled fields and remove any that should not be part of the template.
- Click Save Template.
The template is saved at the project level and available to all project members.
Create a template from scratch
To build a template without starting from an existing item:
- Navigate to the project where you want the template.
- Open Project Settings from the project sidebar.
- Go to the Templates section.
- Click Create Template.
- Fill in the template fields:
| Field | Description |
|---|---|
| Template name | A descriptive name shown when selecting templates (required) |
| Template description | Explains when and why to use this template |
| Title pattern | Default title for items created from this template. Can include placeholders. |
| Description | Rich text content that populates the work item description |
| Default state | The workflow state new items start in |
| Default priority | Priority level applied to new items |
| Default labels | Labels automatically added to new items |
| Default assignees | Members auto-assigned to new items |
| Default estimate | Effort estimate pre-filled on new items |
| Default due date offset | Number of days from creation to set as the due date |
- Click Save Template.
Title patterns
Templates support dynamic title patterns with placeholders:
| Placeholder | Replaced with | Example |
|---|---|---|
{date} | Current date in YYYY-MM-DD format | Weekly Review - {date} becomes Weekly Review - 2026-04-01 |
{project} | Project name | [{project}] Bug Report becomes [Web App] Bug Report |
{user} | Name of the creating member | Onboarding: {user} becomes Onboarding: Alice Chen |
If no placeholder is used, the title is copied exactly as written in the template.
Use a template when creating a work item
- Open the work item creation form (click Create Work Item or press
C). - Click the Template dropdown at the top of the form.
- Select a template from the list.
- The form fields are populated with the template's defaults.
- Modify any fields as needed for this specific item.
- Click Create Work Item.
TIP
Applying a template does not lock any fields. Every value can be changed before creation. The template is a starting point, not a constraint.
Template selection in quick add
When using the quick-add flow (pressing C in the list view), you can also apply a template:
- Press
Cto open quick add. - Click the template icon in the quick-add bar.
- Select a template.
- The title is pre-filled (you can edit it inline).
- Press Enter to create.
Other fields from the template (description, priority, labels, etc.) are applied automatically.
What a template includes
Templates can contain any combination of the following fields:
| Field | Included | Behavior when applied |
|---|---|---|
| Title pattern | Optional | Pre-fills the title field |
| Description | Optional | Pre-fills the description editor with formatted content |
| State | Optional | Sets the initial state (overrides project default) |
| Priority | Optional | Sets the priority level |
| Labels | Optional | Adds the specified labels |
| Assignees | Optional | Assigns the specified members |
| Estimate | Optional | Pre-fills the estimate value |
| Due date offset | Optional | Calculates due date as creation date + offset days |
| Module | Optional | Associates the new item with a module |
Templates do not include:
- Specific cycle assignment (cycles are time-bound and change frequently)
- Attachments (files are not stored in templates)
- Relations (these are specific to individual items)
- Comments (templates are for initial creation state only)
Manage templates
View all templates
- Open Project Settings from the project sidebar.
- Navigate to the Templates section.
- All templates for the current project are listed with their name, description, and creation date.
Edit a template
- In the Templates list, click on the template you want to modify.
- Update any fields.
- Click Save.
Changes to a template do not affect work items that were already created from it. Only future uses of the template will reflect the updates.
Duplicate a template
To create a variation of an existing template:
- In the Templates list, click the three-dot menu next to the template.
- Select Duplicate.
- A copy of the template is created with "Copy of" prepended to the name.
- Edit the copy to make your changes.
Delete a template
- In the Templates list, click the three-dot menu next to the template.
- Select Delete.
- Confirm the deletion.
Deleting a template does not affect work items previously created from it.
WARNING
Template deletion is permanent. If a template is widely used by the team, consider renaming it or adding a note to its description rather than deleting it.
Template gallery
SetGet provides a gallery of built-in templates to help teams get started quickly. The gallery includes common patterns for software development, design, operations, and general project management.
To browse the gallery:
- Open Project Settings and go to the Templates section.
- Click Browse Gallery.
- Preview any template by clicking on it.
- Click Use Template to add it to your project.
Built-in gallery templates can be customized after adding them to your project. They behave exactly like templates you create from scratch.
| Category | Example templates |
|---|---|
| Engineering | Bug Report, Feature Request, Technical Debt, Spike/Research |
| Design | Design Review, Usability Test, Design System Update |
| Operations | Incident Report, Runbook Task, Infrastructure Change |
| General | Meeting Follow-up, Decision Record, Onboarding Checklist |
Template permissions
| Role | Can create templates | Can edit templates | Can delete templates | Can use templates |
|---|---|---|---|---|
| Admin | Yes | Yes | Yes | Yes |
| Member | Yes | Own templates only | Own templates only | Yes |
| Viewer | No | No | No | Yes (when creating items) |
Best practices
- Create templates for your top three item types — Most teams have a small set of work item patterns (bug, feature, task). Start with templates for those.
- Write thorough description templates — Include section headers, checklists, and placeholder text in the description. This guides the creator to fill in the right information.
- Use labels in templates — Automatically labeling items by type (e.g., "bug", "feature") ensures consistent categorization without relying on the creator to remember.
- Assign default owners thoughtfully — Only set default assignees when there is a clear owner for that type of work. Otherwise, leave the assignee empty.
- Review templates quarterly — As your workflow evolves, update templates to match. Remove templates no one uses and add new ones as patterns emerge.
- Use title patterns for recurring items — Combine templates with Recurring Work Items for fully automated, consistently structured task creation.
Related pages
- Work Item Overview — Create, track, and manage work items
- Recurring Work Items — Automate repeating tasks
- Draft Work Items — Save incomplete items for later
- Create via URL — Pre-fill fields with URL parameters
- Work Item Properties — Complete property reference
- Labels — Categorize items with labels