Best Jira recurring issue apps (2026)

If you need recurring issues in Jira — a weekly report, a monthly close, a daily standup task — the apps in this category all look similar on paper. The real differences are the ones buyers complain about in reviews: timezone and daylight-saving accuracy, whether it burns your Jira Automation quota, and whether failed runs retry. This guide compares the options on those lines, so you pick one that fires on the right day rather than one with the longest feature list.

Can Jira do recurring issues on its own?

Partly, and it’s worth knowing the limit before buying. Jira Automation can create issues on a schedule, but every run consumes your metered automation executions — on a busy site you can exhaust the monthly allowance fast — and building correct, timezone-aware recurrence by hand is fiddly. A dedicated recurring-issue app exists to run the schedule reliably without eating your automation quota. Whether a given app actually avoids that quota is one of the key things to check.

The main Jira recurring-issue apps, compared

Ratings and installs are from a 2026 research pass and drift over time — read them as relative scale.

App	Vendor	Rating	Installs	Notes
The Scheduler	TTPSC	4.2★	~3,000	Largest base, older app
Recurring Tasks for Jira Cloud	Big Fig Tree	3.5★	~1,570	Biggest dedicated recurring app; reviews cite timezone + reporter bugs
Repeating Issues for Jira	Codedoers	—	~690	Mid-size
Issue Scheduler – Plan Recurring Tasks	Appsvio	—	~260	Markets the automation-cost angle
Cadence	Datum	New	—	Forge, no automation-quota use, DST-correct

The honest read: The Scheduler has the biggest install base (an older app), and Big Fig Tree’s Recurring Tasks is the biggest dedicated-recurring option — but it carries a 3.5★ rating with reviews specifically citing timezone/DST errors and the reporter field not saving. That’s the category’s recurring weakness. There’s also a pack of brand-new Forge entrants (including Cadence) with few installs and no reviews yet — the field is wide open for a reliable one to earn the reviews.

At a glance: which app fits your situation

This table checks each app against the buyer-decision points above. ✓ = confirmed, ⚠ = partial / unverified either way, ✗ = confirmed gap. Sourced from each app’s Marketplace listing and public reviews (checked October 2026).

Decision point	Cadence	Recurring Tasks (Big Fig Tree)	The Scheduler (TTPSC)	Native Jira Automation
Free tier	✓ Free plan, up to 5 active schedules, any site size	⚠ Free only for sites ≤10 users, then paid per user	⚠ Free only for sites ≤10 users, then paid per user	✓ Included, but execution-metered
Doesn’t consume Jira Automation quota	✓ Own scheduler	✓ Own scheduler	✓ Own scheduler	✗ It is the metered quota
Timezone / DST correct	✓	✗ 2024 review: “Time zones broken. Cloned recurring tasks are being created at different times even if they have the exact setting.”	⚠ No bug reports found in public reviews, not independently verified	⚠ No built-in DST handling; accuracy depends on how the rule is built
Business-day scheduling (skip weekends)	✓	✗ Not mentioned in the listing or changelog	✓ offers business-day scheduling options	✗ No native weekend-skip condition
No cron syntax required	✓ Friendly recurrence UI; cron optional	⚠ Has a GUI, but a 2020 review reports it breaking down to cron for daily schedules: “I can’t select time for the daily through UI (I don’t want to learn cron)”	✓ User-friendly picker; Quartz cron offered only as an advanced option	✓ Rule builder UI, no cron
Missed-run backfill / retry	✓	✗ Not mentioned in the listing	⚠ Admin view surfaces “failed executions”; no confirmed auto-retry or backfill	✗ A missed run is just missed
Runs on Atlassian (Forge, no egress)	✓	✗ Not Forge/Runs-on-Atlassian compliant	✗ Not Forge/Runs-on-Atlassian compliant	✓ Native Jira feature
Proven track record (installs / reviews)	✗ New, 0 reviews yet	⚠ ~1,570 installs, 3.5★ / 38 reviews	✓ ~3,010 installs, 4.2★ / 68 reviews — largest base	✓ Ships with every Jira site

Pick Cadence if you want timezone-correct, backfilled recurring issues that don’t touch your Jira Automation quota — and you’re comfortable being an early adopter with no review history yet. Pick The Scheduler if the largest proven track record matters more to you than running inside Atlassian’s Forge sandbox. Be cautious with Big Fig Tree’s Recurring Tasks for anything time-sensitive — its own reviews document the timezone and cron-UI issues above. Stick with native Jira Automation only if your recurring volume comfortably fits inside your plan’s monthly execution allowance and you don’t need weekend-skipping or missed-run recovery.

What actually separates these apps

• Timezone / daylight-saving accuracy. This is the single biggest source of 1-star reviews. A schedule that fires an hour or a day off — especially across a DST change — makes the app untrustworthy. Confirm it’s handled.
• Automation-quota impact. Apps built on Jira Automation consume your metered executions; apps with their own scheduler don’t. If you’re near your limit, this is decisive.
• Business-day / weekend handling. Recurring work often shouldn’t land on a Saturday. Check whether the app can skip weekends or target business days.
• Retry on failure. A missed run that silently vanishes is a quiet data-integrity problem. Good apps retry or backfill.

Where Cadence fits (and where it doesn’t)

Cadence is Datum’s entry, and it’s deliberately reliability-first — built to fix the exact things the incumbents’ bad reviews complain about:

• Correct timezone and daylight-saving handling — the schedule fires on the day you meant, through DST changes.
• Its own scheduler — no Jira Automation quota used. Recurring issues don’t eat your metered automation executions.
• Business-day scheduling and missed-run backfill — skip weekends or hit business days, and a missed run gets backfilled rather than lost.

The honest limit: Cadence is new, so it has no review history yet — it’s betting on being the reliable option in a field where the established players have accuracy complaints, but it hasn’t accumulated the reviews to prove it at scale yet. If you need a long proven track record today, the incumbents have more installs (and the known bugs that come with them). If timezone correctness and not burning your automation quota are what you care about, that’s precisely what Cadence is built for.

For the hands-on side, see how to create recurring tasks in Jira and how to create a monthly recurring task in Jira.

How to decide, quickly

1. Near your automation quota? Pick an app with its own scheduler that doesn’t consume executions.
2. Burned by wrong-day firing before? Prioritise timezone/DST accuracy over everything — check recent reviews for it.
3. Recurring work can’t land on weekends? Confirm business-day or weekend-skip support.
4. Want the biggest proven base? The Scheduler leads on installs; weigh that against the category’s accuracy track record.

In this category, the boring criteria win: an app that fires on the right day, retries a miss, and doesn’t eat your automation quota beats one with twice the features and a timezone bug.