SupportBook a demoExplore the apps
Templates · · 2 min read

Recurring work items in Jira Cloud: your options

Three ways to create recurring work in Jira Cloud: clone by hand, a scheduled Jira Automation rule, or a template set on a schedule. When each one fits.

Every team has work that comes back. A weekly review, a monthly report, a quarterly vendor check, a release that needs the same steps each time. Jira Cloud has no “repeat” button on a work item, so teams find their own way. Here are the three we see most often, and where each one fits.

1. Clone it by hand

Someone keeps a “master” work item and clones it when the time comes.

  • Good for: work that comes back a few times a year, where one person owns it.
  • Watch out for: it depends on memory. Clones also copy stale details, like last month’s dates and comments, unless someone cleans them up.

2. A scheduled Jira Automation rule

Jira Automation can run a rule on a schedule and create a work item. It is built in, and for one work item with a few fields it works well.

  • Good for: a single recurring work item with a fixed summary and assignee.
  • Watch out for: each level of a structure is another action in the rule. An epic with five work items and their subtasks becomes a long rule that only an admin can change, and a rule that is hard to read is hard to trust.

3. A template set on a schedule

This is what we built AppsDelivered Templates for. A template set holds a whole structure: the epic, the work items under it, their subtasks and checklists. You put the set on a schedule, and the app creates the full structure each time.

  • Good for: recurring work with more than one level, such as an access review with a subtask per system, or a release with a checklist per step.
  • What you get: schedules from every minute to yearly, or a custom CRON expression, in your time zone. A calendar view of upcoming runs. Variables such as $today and $nextWeek in summaries and descriptions, so each run carries its own dates.

How to choose

Ask two questions:

  1. How many levels does the work have? One work item: Jira Automation is fine. An epic with children, or a work item with subtasks and checklists: use a template set.
  2. Who changes it? If the people who run the process should be able to change its steps, a template set is easier to edit than a rule.

Whichever you pick, write down who owns the recurring work. The schedule makes sure the work item exists. The owner makes sure it gets done.

Riley Venable co-founded AppsDelivered in 2017 and leads its engineering as CTO. He builds the Forge apps behind AppsDelivered Templates, Comments and Feeds. More about Riley

All posts
Templates ·

Variables in Jira templates: fill in what changes

Templates ·

New hire onboarding in Jira with one template set

Templates ·

A Jira release checklist you build once