Issue Templates by AurumFlux

Documentation · Jira Cloud · built on Atlassian Forge

Write an issue tree once as a template, then add it under any issue from that issue's ••• menu. Every apply is checked against the project's current configuration before anything is created, and is rolled back if a create fails part-way.

Walkthrough: How to make a Jira Epic template with sub-tasks — Clone vs an Automation rule vs a template.

Install

Install from the Atlassian Marketplace listing. The app adds an Issue Templates page under Apps in your Jira site, and a project-scoped page inside each project.

It asks for three permissions: read Jira work, write Jira work, and app storage. It makes no network calls outside Atlassian.

Create a template

Open Apps → Issue Templates and fill the New template form.

FieldWhat it does
NameHow the template appears in the library. Must be unique.
ScopeGlobal (every project), Project (one project, set the key below), or Personal (only you).
Project keyOnly used when scope is Project, e.g. ENG.
CategoryA free-text label shown next to the template, e.g. Delivery.
Root issue typeThe type of issue the template is added to, e.g. Epic or Task. An Epic template is applied from an Epic.
Root summaryA name for the top of the tree. The issue you apply the template to keeps its own summary.
DescriptionOptional. Filled into the issue you apply the template to, only if that issue's description is empty. May contain variables.
ChildrenThe tree, one issue per line. See below.
VariablesComma-separated names you will be asked for at apply time.

Writing the child tree

One issue per line, in the form Type: Summary. Indent two spaces for each level down. Up to four levels.

Task: Cut release branch {{version}}
  Sub-task: Freeze main and tag {{version}}
  Sub-task: Run migration dry-run
Task: Verify on staging
  Sub-task: Smoke-test the checkout path
Task: Ship to production

The type name must match the project's own name for that issue type. Sub-task and Subtask are different strings, and a project that calls it one will refuse the other. The app tells you which name it expected rather than guessing.

Variables

Write {{name}} anywhere in a summary or description, and list name in the Variables field. At apply time you are asked for a value for each one, and every occurrence is replaced before the issue is created.

Apply a template

Open the issue the template should go under (for an Epic template, open an Epic). Click ••• (More actions) at the top right of the issue and choose Apply template. Pick the template, type any variable values as name=value separated by commas, e.g. version=2.1, owner=Sam, and click Apply. What happens, in order:

  1. The template is checked first. The app reads the project's current issue types and create-screen fields. If the template asks for an issue type or a field the project no longer has, if a child would sit at the wrong level, if the issue you opened is at a different level from the template's root (an Epic template opened on a Task), or if the project requires a field the template does not fill, the whole apply is refused and it names what does not match. Nothing is created.
  2. The children are created under the issue you opened, parents before children, and each new issue key is recorded as it is made. The issue you opened is never deleted or renamed.
  3. If a create still fails (for example a workflow validator refuses it), every issue that apply already created is deleted, children first, and the result lists what was removed. Deleting uses your own permissions: anything you are not allowed to delete is named in the result, so an admin can remove it.
  4. If you apply twice, the second attempt returns the first result instead of building a second tree. An attempt still running is reported as in flight rather than duplicated.

Editing and deleting

Use Edit in the library to change a template in place, and Delete to remove it. Deleting a template does not touch issues that were created from it. Uninstalling the app removes its stored data for that site, on Atlassian's Forge data-retention schedule.

What v1 does not do

Permissions and what Jira will still refuse

The app calls the Jira API as the person applying the template, with that person's permissions. A required field the template does not fill is caught before anything is created. If a project's permission scheme or a workflow validator blocks a create part-way, Jira refuses it and the app reports that refusal back to you and rolls the apply back as far as your permissions allow. It does not work around your site's configuration.

Data and privacy

Template definitions and a short record of each apply are held in Forge storage inside Atlassian's infrastructure. An account ID is stored only for personal-scope templates, so that only you see them. Nothing leaves Atlassian's platform. Full detail is in the privacy policy; the terms of service cover the rest.

Support

Email hello@aurumflux.co. We aim to answer within two business days. Tell us the project key, the template name, and what you expected to happen; if an apply was rolled back, the result message names every issue it removed and that message is the most useful thing to paste.