Blog · 16 September 2026

Jira recurring tasks: Automation, cloning, or a scheduling app?

Jira has no "repeat this task" checkbox, so recurring tasks in Jira Cloud come from one of three places: you clone the issue by hand each cycle, you build a Jira Automation rule with a scheduled trigger, or you install a Marketplace app that creates the issue on a schedule. Cloning is free and forgettable. Automation is built in and flexible, but every run draws on a monthly allowance shared with the rest of your automation. A scheduling app costs a licence above ten users and gives you a purpose-built editor instead. This guide walks through each option, what it costs as of September 2026, and who should pick which.

The short verdict

• A handful of simple recurring tasks, and plenty of automation allowance left? Use Jira Automation. You already pay for it.
• Lots of recurring tasks, or automation usage that already runs close to the limit? A scheduling app keeps recurring work out of the automation budget.
• You need cron expressions, or one template shared across many projects? Look at an incumbent that offers those, such as Issue Scheduler.
• You want schedules that respect working days, a clear record of every run, and rules scoped to one project? That is what Recurring Work Items for Jira is built around.

What counts as a recurring task in Jira

Most teams mean the same few kinds of work: a weekly infrastructure check, a monthly access review, a quarterly report, sprint ceremonies, a certificate renewal, a backup restore test. Each one is the same ticket every cycle, with a different date in the title and a new due date. The failure mode is not complexity. It is that somebody has to remember, and the one cycle nobody remembers is the one the audit asks about.

So whichever route you take, judge it on three things: does the ticket reliably appear, does it look right when it does (title, assignee, due date, subtasks), and can you tell afterwards what happened when it did not.

Option 1: Clone the issue by hand

Open last cycle's ticket, choose Clone from the issue menu, and change the dates and assignee.

Good for: one or two tasks that come up rarely, on a team where one person owns them.

Costs: nothing in money. The cost is attention: it depends on a person, a calendar reminder and a Monday that goes to plan. It also gives you no history of the cycles that were skipped, because a skipped clone leaves no trace at all.

Option 2: Jira Automation's scheduled trigger

Jira's built-in automation can create issues on a schedule. In the project's automation settings you create a rule with the Scheduled trigger, set how often it runs, and add an action that creates the issue, with the summary, assignee and description you want. Smart values let you put dates into the title.

Good for: teams already comfortable with automation, with a small number of recurring tasks, who want everything in one place and no extra app.

What to watch — usage. As of September 2026, Atlassian's own documentation describes automation usage for Jira Cloud as a monthly allowance of steps, where the trigger, each condition, each branch and each action all count, and usage is pooled across the Atlassian apps in your organization:

The same page says that without extra usage enabled, automation flows stop running until usage resets, and with it enabled additional steps are charged at $0.50 per 1,000. A recurring-task rule is only a few steps per run, so on a paid plan a few weekly rules barely register. The risk is the shared pool: when something else — a noisy transition rule, a sync with another tool — exhausts it, your recurring tickets stop along with everything else, and nothing in the backlog tells you they are missing.

Other things to know: a rule is a general-purpose flow, so a recurring task with subtasks, a computed due date and "skip public holidays" becomes a rule with branches and conditions that the next admin has to read. That is fine for people who like building rules, and a maintenance burden for teams who just want the ticket.

Option 3: A Marketplace scheduling app

Several Atlassian Marketplace apps do only this job. Here is how the established ones describe themselves on their Marketplace listings, with their published annual cloud prices, read in September 2026. All four are free for up to 10 users.

Prices are the vendors' own list prices on the Atlassian Marketplace as of September 2026; check the listing before you buy, since they change.

The Scheduler

The most-installed app in the category on the Marketplace. Its listing describes creating an issue once and scheduling it so Jira creates it for you, managing scheduled issues from a project tab panel, and scheduled issues that carry sub-tasks — either built from scratch or taken from an existing issue used as a template. Stay with it if your team already has a large set of scheduled issues in it and they work: switching carries a real rebuild cost.

Issue Scheduler (Appsvio)

Built around scheduled templates. Its listing describes daily, weekly or custom intervals, a cron definition when you need one, variables in the summary and description, subtasks and stories, and templates that can be private, public or cross-project. Stay with it if you rely on cron expressions or share one template across several projects.

Recurring Tasks for Jira Cloud (Big Fig Tree)

A focused scheduler with a wizard for defining a task, a list of configured tasks, and an execution history showing the last run's status. Stay with it if a simple list and wizard is all your team needs and it has been reliable for you.

Repeating Issues for Jira (Codedoers)

Works from the issue outward: its listing describes recurring actions on an issue — clone it, create sub-tasks, reopen it — with a custom recurrence, plus support for non-working days and project rules that set a repeating up when an issue is created. Stay with it if your recurring work is really "reopen this same ticket" rather than "create a fresh one".

Recurring Work Items for Jira

This is our app, so read this section as the maker's description; everything in it is documented on the rules guide. A rule is a schedule plus an issue template, set up once inside one Jira project:

• Schedules: every day, every week on chosen weekdays, every month on a date, or every month on a weekday such as "the last Friday" — each with an "every N" interval. There is no cron field; the editor shows the next five runs live as you type, so you can check a schedule before saving it.
• Time zones done properly: the time is a wall-clock time in a real time zone, so a rule set for 09:00 Europe/London stays at 09:00 through the clock change.
• Working days and holidays: the project admin sets the working week and a holiday list once, and each rule chooses whether a run that lands on a non-working day runs anyway, moves to the next or previous working day, or is skipped. The due date moves with it.
• The ticket looks right: dynamic titles and dates such as {{now.monthName}} access review, a due date counted from each run, reporter, assignee, priority, labels, parent, other fields from the create screen, and up to 10 subtasks per run.
• It does not pile up: optionally create nothing while the previous issue is still open, and choose what happens to runs missed while the app was unavailable — one catch-up issue, none, or one per missed run.
• You can see what happened: every run — created, skipped or failed — is recorded in the rule's history with the reason, and a daily health check flags a rule that keeps failing.

It consumes no Jira Automation usage: scheduling is the app's own and never creates or runs an automation rule. It runs entirely on Atlassian's infrastructure and declares no external domains, which is why it carries the Runs on Atlassian badge. Runs happen within about five minutes of the time you choose.

Not the right fit if you need cron expressions, a single template shared across projects, or a Server or Data Center build — rules are scoped to one project at a time and the app is Jira Cloud only.

How to choose

Ask these questions in order:

1. How many recurring tasks, and how complicated? Two simple ones: Automation or even cloning. Twenty with subtasks and due dates: a dedicated app pays for itself in admin time.
2. How close does your organization run to its automation allowance? Atlassian's documentation points to the Usage tab under Settings → System → Automation flows. If recurring tickets stopping mid-month would matter, keep them off the shared pool.
3. Do weekends and holidays change the date? If a task "due before the month starts" must never land on a Saturday, you want working-day handling built in rather than rebuilt in conditions.
4. Who needs to know when a run did not happen? Pick the option whose history you can actually read.
5. What does it cost at your seat count? Below 10 users every app here is free; above it, compare the table.

How to switch to a scheduling app

Whichever app you move to, the safe order is the same:

1. List what you have. For Automation, export or screenshot each scheduled rule: schedule, time zone, summary, assignee, due date logic, subtasks.
2. Install the app and turn it on for one project first. For Recurring Work Items, that is installing it and then enabling the project and setting its working week.
3. Recreate one rule and compare its next-run preview with the schedule you are replacing.
4. Disable the old rule before the new one's first run. Running both creates duplicate tickets, and duplicates are the one migration mistake everyone on the team notices.
5. Check the first real run in the issue list and in the app's run history, then move the rest.

Frequently asked questions

Can Jira create recurring tasks without an app? Yes — Jira Automation's scheduled trigger with a create action does it, subject to your plan's automation usage.

Do recurring tasks count against automation limits? Rules in Jira Automation do. A Marketplace app that schedules on its own does not; check each app's documentation for how it schedules.

Can a recurring task create subtasks? In Automation, with extra actions. The Scheduler, Issue Scheduler and Recurring Work Items all describe subtasks as part of the scheduled issue.

Are these apps free? Every app in the table above is free for teams of up to 10 users on Jira Cloud; paid tiers start above that.

Ready to try the project-scoped approach? See how Recurring Work Items for Jira works, or go straight to writing your first rule.