Bug reporting process
Report, triage and verify every bug with the same steps.
1 bug, 3 subtasks
See the template set| Template | Builds | Runs | Next run |
|---|---|---|---|
| Sprint kickoff | 1 epic, 4 work items | On request | When applied |
| Monthly access review | 1 work item, 6 subtasks | Monthly | Tue, Dec 1 |
| Weekly review | 1 work item, 3 subtasks | Every Friday | Fri, Nov 27 |
| Versioning and release | 1 work item, 9 checklist items | On request | When applied |
| New hire onboarding | 1 epic, 4 work items | On request | When applied |
One template set creates the epic, its work items and their subtasks, with fields, checklists and variables already filled in.
Run a template set every week, month or quarter, in your time zone. The work is there before anyone asks for it.
Pick a template in Jira's own Create dialog to fill in a work item, or apply one from a work item's More menu.
Lay out the epic, the work items under it and their subtasks. Set the work type, fields and checklist for each one. Apply it, and Jira gets the whole structure. Or add its work items under an epic you already have.
Illustration of the app in Jira Cloud, with sample data.
Pick a template in the Template field, and the work item's fields fill in before you click Create.
Apply a template from the work item's More menu to fill in its fields. To add a template set's work items under an existing epic, pick that epic as the parent when you apply the set.
Hourly, daily, weekly, monthly or yearly, or your own CRON schedule, in your time zone. See every upcoming run before it happens.
In a company-managed space, add a template or a whole template set to a workflow transition, so moving a work item to Approved applies it.
Call the app's API from an Automation rule or your own script, for example when a sprint starts.
Variables fill in dates, keys and the sprint number in summaries and descriptions, and user variables set the assignee. Checklists split each work item into steps, so the team sees what done means.
$sprint$today$projectKey$teamLead$today and $projectKey are built in. You add $sprint and $teamLead to the template set.
In Jira's Create dialog, a template fills in one work item:
Illustration of the app in Jira Cloud, with sample data.
Choose the spaces and work types where each template appears.
See which templates run, where and how often.
Manage every template set, schedule and variable from the app's admin pages.
Turn them on, and a template keeps what people already typed in the Create dialog. On an existing work item, it fills only empty fields unless someone chooses to update all fields.
Start from one of these, then change it to fit your team.
| Feature | Jira | AppsDelivered Templates |
|---|---|---|
| Repeat work on a schedule | Set to recur copies a work item and its child work items daily, weekly or every two weeks. | Template sets run hourly, daily, weekly, monthly or yearly, or on your own CRON schedule, in your time zone, and the app lists every upcoming run. |
| Start from a saved structure | Clone copies an existing work item, and can include its child work items. | A template set is a saved structure: the epic, its work items, subtasks and checklists, kept apart from live work, with variables filled in when it runs. |
Last checked November 2026.
The app is built on Forge and is part of Runs on Atlassian, so it runs on Atlassian's cloud and keeps its data there.
Yes. When you apply a template set, pick an existing epic or feature as the parent. The set adds its child work items under it.
Yes. Call the app's API from an Automation rule to apply a template set when your rule fires.
Yes. It supports Jira Data Center 8.12 to 11.3.
English and German.
Building Jira apps since 2017.
Free for up to 10 users. Larger teams get a 30-day free trial, then pay per user, billed by Atlassian.