Stencil Issue Templates for Jira

Templates that fire where you actually create work items — not only from one special button. Fields, descriptions, whole epic → story → sub-task trees, placeholders and prompted variables. One edition, everything included, US$0.79 per user per month and free for teams of ten or fewer.


Getting started

1. Install

Install from the Marketplace listing, or in Jira go to Apps → Explore more apps and search for Stencil Issue Templates for Jira. You need to be a Jira administrator.

2. Create your first template

  1. Go to Project settings → Apps → Stencil Work Item Templates.
  2. Choose New template and give it a name.
  3. Fill in the fields you want pre-filled — summary, description, labels, components, assignee, and any custom field.
  4. Use variables like {{customer}} in the summary or description for values you want to be asked for each time.
  5. Save.

3. Apply it

  1. Open a work item and choose Apply a Stencil Template from the … menu, or
  2. Set the template to apply automatically on create for chosen work item types, in the template's own settings.
  3. If the template uses variables you are prompted for them, and you choose what happens when a field already has a value.

4. Share across projects

Go to Settings (cog) → Apps → Stencil Site Template Library to keep templates every project can use.

If something looks wrong

The problem every other template app has

Read the one- and two-star reviews of any issue-template app for Jira Cloud and the same sentence comes back for years:

"Working fine for the normal create button in the top-navigation but sadly not for the 'create issue'-button in the backlog."

"The extension does not trigger if you create a task/bug/story from within an epic. This is the way that 50% of all issues are created for us."

They are right, and the cause is real: Jira gives an app one hook on one create screen. So Stencil does not rely on that hook alone.

On the global Create dialog, Stencil fills the fields live, as you pick the issue type — you see them appear and you can edit any of them before you save.

Everywhere else, Stencil applies the template the moment the work item is created: the backlog inline-create row, the board's quick-add, the "create child" control inside an epic, sub-tasks from the issue view, the mobile apps, Jira Service Management portal requests, CSV imports, the REST API, and work items created by Automation rules.

The result is identical. Outside the Create dialog it arrives a few seconds after you save rather than while you type — we say so here, in the app, and in our documentation, because no Forge app can do better today and you deserve to know that before you buy.

Two more things we would rather you heard from us than found out:


What it does

Templates that are actually structures

A template is a tree, not a text snippet. An epic with three stories, each with its own sub-tasks, created in the right order with the right parents — up to 300 work items and four levels deep. Any item can also be created and linked rather than nested, using any Jira link type you have.

Every field, not five

Anything Jira's create API accepts: summary, description, labels, components, priority, assignee, due date, versions, environment — and every custom field on your screens, addressed by its own id. There is no list of "supported fields" for your most important field to be missing from.

Placeholders and prompted variables

Summary:  {{project.key}} release checklist — {{var.release}}
Due date: {{today+5w}}
Assignee: the parent work item's assignee

Date arithmetic is done on the calendar, so "due in seven days" is seven days across a daylight-saving change — not six or eight.

Conditions, including JQL

Any item in the tree can carry conditions: twelve fields (summary, description, issue type, project, priority, labels, components, status, reporter, assignee, JSM request type, or one of your own variables) against seven operators including regular expressions — and a JQL condition, so "only create the security-review sub-task when the parent matches this filter" is one line. An item that is conditioned away takes its whole subtree with it, so you never get a child whose parent was skipped.

The category leader charges extra for JQL conditions. They are on the base plan here.

Defaults, per issue type and per request type

Set the default template for an issue type — or for a Jira Service Management request type, which nobody else does — at project level, at site level, or both, with a documented precedence. New work items of that type get the template automatically, wherever they are created from.

Change the issue type and the content changes with it

Start a Bug, get the bug template, realise it is a Story, switch — and Stencil re-evaluates instead of leaving the bug template's headings behind. It replaces only the values it wrote itself and which nobody has edited since; the moment you type in a field, that field is yours and no template will ever overwrite it.

It will not leave you with orphaned child tickets

Jira delivers create events at least once, which is why "our templates started creating orphaned child tickets" is a real review of a real competitor. Stencil records what it has created on the work item itself, before it creates anything, so:

Save an existing work item as a template

Point at an epic you already like and turn it — and its whole child tree — into a template in one step. Absolute due dates become offsets ("seven days after the template is applied"), because copying last March's due date is never what anybody meant.

Global and per-project libraries

A site-wide library plus a library per project. A project template with the same name as a global one shadows it, so a team can have their own version of the bug template without a site admin's involvement. A global template can be restricted to a named list of projects.

Search what your templates did

The record Stencil keeps is a Jira entity property, so it is JQL-searchable:

stencilTemplate ~ "Security review"  AND  stencilApplied >= -30d
stencilChildren > 5

Reporting and an audit log, free

Who applied which template, to what, when, how long it took, how many work items it created, and what was skipped — with a usage report over the top and CSV export. The category leader sells both of these only in its more expensive edition.

Jira Automation

A first-class Apply issue template action with typed outputs, so a later step in the same rule can branch on whether it worked and how many work items it created. Triggered by a transition, a schedule, a webhook — anything Automation can trigger on.

A rule runs with the app's own access rather than the rule author's, and it names the work item by key, so each project's administrator switches this on for their own project before rules can write to it. It is one toggle in the project's settings, and it is off until they turn it on — because "any project admin can author a rule that edits any project" is not a default we were willing to ship.

Create-screen field rules

A template can hide a field, mark it required, or replace its help text on the global Create dialog. (This is a guard on that dialog, not site-wide validation — REST and CSV import bypass it, as they bypass every app's.)


Runs on Atlassian

Stencil declares no external fetch permission at all. It is not technically capable of contacting any host outside Atlassian's own APIs. Your issue content, your templates and your audit log never leave your Jira site, and data residency follows it.


Limits, published

300 work items per template · 4 levels deep · 500 templates per library · 25 prompted variables per template. Children are created 50 at a time with Jira's bulk endpoint, one level at a time, paced against Jira's own write limits, and large trees are handed to an async queue so nothing runs against a timeout.


Pricing

Free for 10 users or fewer. US$0.79 per user per month above that, with the usual volume tiers.

One edition. Everything on this page is included. There is no Advanced tier holding default-template-per-issue-type, JQL conditions, usage reports or the audit log hostage — which is exactly how the category leader prices, and it is the main reason this app exists.


Support

Documentation, a support address and an issue tracker are linked from this listing. Questions and bug reports get a reply.