How to create recurring issues in Jira

UPDATED 2026 · 6 MIN READ

Recurring work is everywhere in a Jira project: the monthly compliance review, the quarterly access audit, the weekly backup check, the month-end close. The obvious question — "how do I make Jira create these automatically?" — has a surprisingly awkward answer. Here's the complete picture, from the native feature to its limits to a clean fix.

Option 1: Native "Set to recur"

Jira Cloud has a built-in recurrence option on an issue's due date, called Set to recur. It's the fastest path, and for simple cases it's all you need. It offers four intervals:

• Daily
• Weekly
• Every weekday
• Every 2 weeks

Option 2: Automation rules with a scheduled trigger

The common workaround is a Jira automation rule using a Scheduled trigger plus a Create issue action. On the Scheduled trigger you can switch to the Advanced tab and supply a CRON expression, which does unlock monthly and quarterly cadences.

This works, but it comes with real friction:

• You're hand-writing CRON, which is error-prone and hard to read at a glance.
• Global and multi-project automation rules count against your plan's execution limit, so a fleet of recurring rules can eat into quota you'd rather spend elsewhere.
• Calendar patterns do work — TUE#2 for the 2nd Tuesday, the lastBusinessDayOfMonth smart value for month-end — but they typically poll daily or weekly to fire once, multiplying the quota cost above.
• Every recurring task lives as its own rule, so managing dozens of them becomes its own chore.

Option 3: A purpose-built recurrence app

This is where a dedicated app earns its keep. Recurring Issues for Jira is built on Atlassian Forge and adds exactly the schedules the native feature is missing, with none of the CRON or quota downsides:

• Monthly on any date — including the last day of the month.
• Quarterly and annually.
• Nth-weekday — the 2nd Tuesday, the last Friday, and so on.
• Skip weekends and holidays, rolling a target forward to the next business day.
• A full template per schedule, including subtasks and prefilled fields.
• It runs on its own Forge scheduled trigger, so it never touches your automation quota.

Which should you use?

If your recurrence is daily or weekly, native "Set to recur" is perfect — use it. If you need anything monthly or longer, or anything tied to the calendar ("first Monday", "last business day"), native recurrence can't do it and CRON automation is a fragile substitute. That's the specific gap Recurring Issues for Jira was built to close.

Add Recurring Issues to Jira — free for up to 10 users

Next: setting up monthly recurring tasks in Jira →

More in this series: the 2nd Tuesday & Nth weekday · last business day of the month · Jira automation vs. recurring issues