Quick Issue Templates for Jira

Documentation & support

Get it on the Atlassian Marketplace Free for teams of 10 or fewer

What this app does

Save any issue as a reusable template — summary, description, labels, sub-tasks and field values such as assignee, priority, due date and custom fields — then create that issue again in one click, in any project you have access to.

Templates are stored inside the app. You do not need to create a separate Jira project to hold them, and you do not need to maintain one.

Getting started

1. Install the app from the Atlassian Marketplace.
2. In Jira, open Apps → Templates in the left sidebar.
3. Click New template.
4. Give it a name, choose the project and issue type, then fill in the summary, description, labels and sub-tasks you want every copy to start with. Optionally, preset field values such as priority or a due date.
5. Click Save.
6. Back on the list, click Create issue next to any template. If the template has placeholders, fill them in and confirm. The issue and all of its sub-tasks are created, and the new issue key is shown.

Next to each template, Duplicate opens an unsaved copy you can rename or point at another project, and Delete asks for confirmation before removing it.

Using placeholders

Anywhere in the summary, description or sub-task titles you can write a placeholder in double braces, for example {{customer}} or {{release}}. When you click Create issue, the app asks for a value for each one and puts it in everywhere that placeholder appears. Placeholders you leave empty stay in the text exactly as written, so nothing is silently lost.

Presetting field values

After you choose the project and issue type, the editor shows Field values. Use Add a field to preset any of these, and every issue created from the template starts with them filled in:

• Priority, components, fix and affected versions
• Assignee, set to the person who creates the issue
• Due date, set as a number of days after the issue is created, so it is right every time
• Custom fields of the common types: single and multiple choice lists, cascading lists, radio buttons, checkboxes, labels, single-line and multi-line text, numbers, dates, date-and-time fields and URLs

Fields your project requires are added automatically, because Jira will not create the issue without them. Placeholders such as {{customer}} work inside text fields too.

Formatting the description

Write the description as plain text and use these marks; the issue gets real Jira formatting:

• # Heading, ## Heading, ### Heading
• - item for bullet lists, 1. item for numbered lists
• **bold**, `code` and [link text](https://example.com)
• Tables as lines like | Task | Owner |. Put |---|---| under the first line to make it a header row.

Text without these marks is created exactly as you typed it, line by line.

Epics with their child issues

Choose an Epic (or any issue type above the base level) as the template's issue type, and the sub-task box becomes Child issues with a Child issue type picker, for example Story or Task. One click creates the Epic and every child under it.

Creating issues automatically

Under Create automatically, set a template to run every day, every week on a chosen weekday, or every month on a chosen day, at a whole hour in UTC. The issue is created within that hour, with its sub-tasks or child issues. The editor shows the result of the last run.

Scheduled issues are created by the app itself, so the reporter is the app and Jira's permissions for apps in that project apply. Placeholders stay as written, except {{date}}, which always becomes the creation date, for example Weekly report {{date}}.

Guides

• How to create recurring tasks in Jira Cloud (with sub-tasks)
• How to clone a Jira issue with its sub-tasks
• How to make a Jira Epic template with Stories

Frequently asked questions

Current limitations

These are known and deliberate for the current version:

• Teams, groups, Assets objects and Jira Service Management request fields cannot be preset yet.
• The project a template belongs to must have a sub-task issue type enabled for sub-tasks to work.

Privacy and data

The app runs entirely on Atlassian's infrastructure. Your templates and your Jira data are never sent to any external server, and the app makes no outbound network calls.

Support

Privacy policy  ·  Security policy  ·  Terms of service