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.
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.
Open Apps → Issue Templates and fill the New template form.
| Field | What it does |
|---|---|
| Name | How the template appears in the library. Must be unique. |
| Scope | Global (every project), Project (one project, set the key below), or Personal (only you). |
| Project key | Only used when scope is Project, e.g. ENG. |
| Category | A free-text label shown next to the template, e.g. Delivery. |
| Root issue type | The type of issue the template is added to, e.g. Epic or Task. An Epic template is applied from an Epic. |
| Root summary | A name for the top of the tree. The issue you apply the template to keeps its own summary. |
| Description | Optional. Filled into the issue you apply the template to, only if that issue's description is empty. May contain variables. |
| Children | The tree, one issue per line. See below. |
| Variables | Comma-separated names you will be asked for at apply time. |
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.
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.
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:
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.
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.
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.
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.