Blog · 22 September 2026

Jira automation templates: what the library leaves out

Jira automation templates are pre-built rules you copy instead of writing — a trigger, a condition and an action already wired together, so you start from something that works rather than from an empty rule editor. They live in Atlassian's own template library at atlassian.com/software/jira/automation-template-library, and as of September 2026 that page describes itself as "Hundreds of Jira automation templates so you never need to start from scratch", "Available to all Jira Cloud customers". What the library is very good at is reacting to something that just happened in Jira or in a tool beside it. What it is thin on is the opposite job — creating the same work item again on a calendar, with nothing having happened at all — and that gap is the reason most people arrive at this page.

What a Jira automation template actually is #

A template is a saved rule definition, not a separate feature. You pick one, it opens in the automation rule editor of your project or site, and from that moment it is an ordinary rule you own: you can change the trigger, add conditions, edit the action, and it runs under exactly the same limits and the same audit log as a rule you typed yourself.

Three places carry them, and they are worth telling apart:

• The public template library — the marketing-side gallery linked above, organised by category and by the tool you want to connect.
• The rule editor's own template picker — the list Jira shows you inside Project settings → Automation → Create rule, which is where a template becomes a real rule on your site.
• The Automation Playground, which the library page describes as "a safe sandbox environment where you can interactively explore 100s of automation templates to see exactly how they work" — useful for reading a rule's wiring before you put it on your own project.

What the library covers, by category #

These are the popular categories the library page itself lists, as of September 2026:

And these are the templates that page currently promotes as popular: publishing a post-incident review into Confluence, auto-assigning a work item raised without an assignee, moving an epic's stories to done when the epic is, sending a daily Slack summary of open sprint items, summing sub-task story points onto the parent, and transitioning a work item when a pull request is merged.

Read that list again and notice what is not in it: not one of them creates a work item on a schedule. Five of the six are triggered by an event in Jira, and the sixth by an event in a code host. The daily Slack summary is the only scheduled one, and it reports rather than creates.

The recurring shapes Jira automation templates leave out #

Automation itself can absolutely be scheduled — a Scheduled trigger plus a Create work item action is a working recurring rule, and we walk six of those end to end in Jira automation examples. The point is narrower: the template library is not where you will find one already assembled, so the recurring case is the case you build by hand. Four shapes in particular you will be wiring yourself:

• "The first working day of the month, not the 1st." A schedule expressed in working days, with your team's weekend and holidays taken into account, rather than a calendar date that sometimes lands on a Sunday.
• "Only if last month's is closed." A rule that skips its own occurrence when the previous issue it created is still open, so an unfinished quarterly review does not stack up four deep.
• "The same parent, with the same five sub-tasks, every time." A whole checklist tree created under each occurrence, not a single issue you then populate.
• "What happened last Tuesday, and why." A per-rule history of every occurrence — created, skipped or failed, with the reason — rather than a global audit log you filter after somebody notices the ticket never appeared.

Each of those is buildable in Automation, and each is a rule you now own and maintain. That is the honest trade: the template library saved you the first rule, not the fifth.

What a rule from a template costs to run #

A template is free to take. The rule it becomes is metered: Atlassian meters automation usage against your plan's monthly allowance, pooled across your organisation, which is why the library page's own footer offers a "free Jira Premium trial for increased automation limits". The current allowances and the rate above them are broken down in Jira Automation pricing.

The practical consequence for recurring work is that the cost follows the shape of the rule, not the number of rules. A scheduled rule that creates one work item is cheap. The same trigger with a JQL search in front of it, looping over a branch per result, spends in proportion to how many issues it matched — and it spends that every time it fires, whether or not anything needed doing.

Jira automation templates vs a scheduling app #

Who should stay with Jira Automation templates #

Most teams, and this is not a hedge:

• Your rules are event-driven. Assign, transition, notify, sync, link — the library has your rule already written, and adding an app for it would be strictly worse.
• You want one tool. Every rule in one place, one audit log, one permission model, nothing else to install or license.
• You have a handful of scheduled rules and they are simple. A weekly ticket on a fixed weekday needs no working-day policy and no overlap rule. Take the Scheduled trigger, add Create work item, and you are done.
• You are not on Jira Cloud. Recurring Work Items is a Forge app; there is no Server or Data Center build, and no Confluence version.

Switch only when the schedule itself is the difficult part — when you find yourself encoding a holiday calendar into a condition, or explaining to somebody why last month's ticket appeared twice.

From a template to a schedule, step by step #

1. Open Project settings → Automation → Create rule and check the template picker for something close to your job.
2. If nothing matches, choose the Scheduled trigger and set the interval or a cron expression — see Jira cron expression for the syntax and the two traps.
3. Add Create work item, and fill the summary from a smart value rather than a fixed string, so consecutive issues are distinguishable.
4. Add the conditions that make it correct for your calendar: a day-of-week check, a JQL condition for an open previous issue.
5. Run the rule manually once, then read the audit log. A scheduled rule that fails does not announce itself; it just stops producing tickets.
6. If steps 4 and 5 are where the work is, that is the signal — the schedule, not the action, is your problem. Recurring Work Items for Jira is built for exactly that half.

Frequently asked questions #

Are Jira automation templates free? Yes. The library is open and, as the page states, available to all Jira Cloud customers. Taking a template costs nothing; running the rule it creates draws on your plan's automation allowance.

Where do I find the templates inside Jira? Project settings → Automation → Create rule, which offers templates before the blank editor. The public library and the Automation Playground are for browsing and reading rules, not for installing them.

Is there a template for a recurring task? Not among the templates the library promotes. The building blocks are there — a Scheduled trigger and a Create work item action — so the rule is quick to assemble; see Jira recurring tasks for the three ways people do it and where each one stops.

Can I make my own template? You can duplicate an existing rule, which is the practical equivalent inside a project. What you cannot do is publish a rule into Atlassian's library.

Do templates work on Jira Server or Data Center? Automation exists on those deployments, though the cloud library's templates assume cloud triggers and cloud integrations. Check the trigger before copying a rule across.