Jira automation for recurring issues: where it works, where it costs you
When Jira's native "Set to recur" runs out of road, the next stop is automation: a scheduled trigger plus a "Create issue" action. It's more capable than people give it credit for — it can do the calendar-shaped schedules too. The real question isn't whether it can, it's what each pattern costs. Here's an honest map.
Where automation is simply the right tool
For a simple, fixed cadence, an automation rule is the answer — don't reach for an app:
- Daily / weekly stand-ups, checks, and reminders.
- Monthly on a fixed date — the 1st, the 15th — via a cron expression on the scheduled trigger.
Calendar patterns: possible, but they cost
Automation can also do the tricky ones — this is where people underestimate it, and also where the bill starts:
- Nth weekday works via Quartz cron notation:
0 0 9 ? * TUE#2is the 2nd Tuesday. (full breakdown) - Last business day works via the
{{now.lastBusinessDayOfMonth}}smart value in a condition. (full breakdown)
Both are legitimate. But notice what they require: cron and smart-value fluency, and — for the last-business-day pattern — a rule that polls daily to fire once a month.
The three real costs
1. Execution quota. Global and multi-project rules count against your plan's automation execution limit. Calendar patterns make it worse: a rule that runs every day (or every Tuesday) to create one issue spends 4–30 executions a month on a single recurring task.
2. Management sprawl. Every recurring task is its own rule, scattered across the automation list — no single place that answers "what recurring work do we have?"
3. Readability. 0 0 9 ? * TUE#2 and {{now.lastBusinessDayOfMonth}} are write-once, debug-never. Six months on, they tell nobody what they're for.
The pattern: automation can do almost anything — it just spends quota, cron literacy, and rule-list clutter to do it. That's exactly what a purpose-built tool removes.
The alternative: a dedicated scheduled trigger
Recurring Issues for Jira runs on its own Atlassian Forge scheduled trigger:
- Calendar-native patterns — monthly, quarterly, annual, every-N-weeks, Nth-weekday, and last-business-day are dropdown choices, not cron.
- Off your automation quota — it never touches your Jira automation executions.
- One management page — every schedule in a single list to pause, edit, or delete.
- Templates with subtasks — each schedule carries the full issue and its checklist.
A fair rule of thumb
A handful of simple or fixed-date schedules, and you're comfortable in cron? Automation is the right call — keep it. Calendar-shaped patterns, quota you'd rather protect, or more than a few recurring rules to manage? That's when hand-built automation turns into overhead, and a dedicated app turns it back into a dropdown.
Add Recurring Issues to Jira — free for up to 10 users
Back to the full guide: how to create recurring issues in Jira