Quick Issue Templates for Jira · Guides

How to create recurring tasks in Jira Cloud

The weekly report, the monthly invoice run, the Monday server check: work that comes back on a fixed rhythm. Here are two ways to make Jira create it for you, including the sub-tasks.

Updated 24 October 2026 · Written for Jira Cloud

Option 1: a scheduled Jira Automation rule

Automation is built into Jira Cloud, so this costs nothing extra. You need permission to create rules (project or Jira administrator).

Go to Project settings → Automation → Create rule.
Choose the Scheduled trigger. Set how often it runs (for example every Monday at 09:00). Leave Run a JQL search unticked, so the rule runs once per schedule rather than once per matching issue.
Add the action Create work item. Pick the project and work type, and fill in the summary and description. A smart value such as {{now.format("yyyy-MM-dd")}} in the summary gives each copy its date.
For sub-tasks, add a Branch rule / related work items and choose Most recently created work item. Inside the branch, add the action Create sub-tasks and enter one sub-task per line.
Name the rule, turn it on, and use Run rule once to check the result.

The branch in step 4 is the part people miss. Without it, there is no work item for the sub-tasks to attach to, because a scheduled rule with no JQL search has no trigger issue.

What to keep in mind

Every run counts toward your Jira plan's monthly Automation usage. A daily rule is about 30 runs a month, so check your plan's allowance if you have many rules.
The content lives inside the rule. To change the description or sub-tasks later, someone has to edit the rule, which usually means an administrator.
Each recurring task is one rule. Ten recurring processes means ten rules to look after.

Option 2: a scheduled template

If you would rather keep recurring work as a template that anyone on the team can read and update, a template app does the same job with less setup.

Quick Issue Templates for Jira

This guide is written by Kelvido, the company that makes this app.

Save the task once, with its description, labels, field values and sub-tasks. Then set it to run every day, every week (on a chosen weekday) or every month (on a chosen day), at the hour you pick (in UTC). The placeholder {{date}} puts the creation date in the summary. The same template can still be created by hand in one click whenever you need an extra copy.

An Epic template creates the Epic and all its child issues on the same schedule.

View on the Atlassian Marketplace

Which one should you use?