Simple Issue Templates

Turn any Jira issue — with its subtasks — into a reusable template. No setup.

What it does

Teams that run the same checklist every week — onboarding, releases, incident response, client kick-offs — end up copying an old issue and tidying the subtasks by hand.

This app saves an issue that is already set up the way you like, including its subtasks, and recreates it on demand.

Not sure you need an app? The comparison guide covers the options Jira already has and when this one is worth paying for.

Setting it up

There is no setup. Install the app and it appears on every issue.

Saving a template

1. Open any issue that is arranged the way you want future issues to look.
2. In the Details sidebar on the right, expand Templates.
3. Optionally type a name. Leaving it blank uses the issue's summary.
4. Click Save as template.

The template captures the summary, description, issue type, priority, labels, assignee, and every subtask with its own summary, description, and assignee.

Using a template

1. Open any issue in the project you want the new issue created in.
2. Expand Templates in the Details sidebar.
3. Click Use next to the template.

A new issue is created in that project, with all of the template's subtasks.

Managing templates

Go to Apps → Issue Templates to see every template on the site and delete any you no longer want. Templates are shared across the whole site, so a template saved by one person can be used by anyone with permission to create issues.

What this version does and does not do

Included: summary, description, issue type, priority, labels, assignee, and subtasks with their own summaries, descriptions, and assignees.

Not included yet: custom fields, attachments, comments, linked issues, components, fix versions, and scheduled or automatic template application. These are on the roadmap. They are listed here so nobody installs the app expecting them.

Known behaviour

If a project has unassigned issues turned off, or a default assignee who lacks the Assignable User permission, the app retries creation with the person applying the template as the assignee rather than failing.

If a subtask cannot be created — usually because the target project does not have the same subtask issue type — the parent issue is still created, and the app reports the exact reason for the subtask that failed.

Permissions the app requests

Scope	Why it is needed
read:jira-work	Read the issue being saved, and its subtasks
write:jira-work	Create the issue and subtasks when a template is applied
read:jira-user	Resolve the current user when a project refuses unassigned issues
storage:app	Store templates in Atlassian-hosted Forge storage

Support

Email support@harvizzle.com. Target first response is two business days.