Recurring Tasks for Jira and The Scheduler alternatives
If you’re looking for an alternative to Recurring Tasks for Jira Cloud (Big Fig Tree) or The Scheduler (TTPSC), the short answer is: both are established apps that work for most teams, and the reasons to switch are specific. Recurring Tasks is the cheapest but rated about 3.5★, with a public review reporting timezone errors. The Scheduler is better rated (about 4.2★) but costs roughly twice as much per user. Neither is a Runs on Atlassian (Forge) app. This guide compares them with Encore, Datum’s recurring-issue app, and says plainly where each one still wins.
Figures below come from the Atlassian Marketplace listings, checked 13 November 2026. They drift over time, so read them as rough scale.
Why teams look for a Recurring Tasks for Jira alternative
Recurring Tasks for Jira Cloud has ~1,550 installs and 38 reviews, averaging about 3.5★. It is actively maintained (several releases in October and November 2026) and does a lot: a scheduling wizard plus cron, a calendar view of past and future runs, one-time future tasks, native checklist support and JSM request support.
The reviews are where buyers hesitate. A 2024 review reads: “Time zones broken. Cloned recurring tasks are being created at different times even if they have the exact setting.” Older 2020 reviews describe the reporter field blocking saves (“Couldn’t mark myself as a reporter (required field) for any tasks. Cannot use.”) and cron leaking into the UI (“I can’t select time for the daily through UI (I don’t want to learn cron)”). Some of this may be fixed since. But for recurring work, firing at the wrong time is the failure that matters most, so it’s worth testing before you rely on it.
Why teams look for a The Scheduler alternative
The Scheduler has the largest install base in the category (~2,940 installs, 68 reviews, about 4.2★) and the deepest feature set: sub-tasks, date variables, scheduler calendars that skip non-business days, a global admin page, and since October 2026, importing Jira Automation rules from JSON. It also runs on Data Center and Server.
The usual reasons to look elsewhere are cost and hosting. Its annual list price for 25 users is $250, against $137.50 for Recurring Tasks. Like Recurring Tasks, it asks for permission to access your data from outside Atlassian, so it is not a Runs on Atlassian app. That matters if your security review prefers apps that keep data inside your Atlassian tenant.
At a glance: Encore vs. Recurring Tasks vs. The Scheduler
✓ = confirmed, ⚠ = partial or not verified, ✗ = not offered. Sources: each app’s Marketplace listing, release notes and public reviews (November 2026).
| Decision point | Encore | Recurring Tasks (Big Fig Tree) | The Scheduler (TTPSC) |
|---|---|---|---|
| Free on sites with ≤10 users | ✓ | ✓ | ✓ |
| Free plan on larger sites | ✓ up to 5 active schedules | ✗ paid per user | ✗ paid per user |
| Annual list price, 25 users | see listing | ✓ $137.50, the lowest | $250 |
| Doesn’t use Jira Automation executions | ✓ own scheduler | ✓ own scheduler | ✓ own scheduler |
| Per-schedule timezone, DST-correct | ✓ | ✗ 2024 review reports timezone errors | ⚠ no complaints found, not verified |
| Business days and holidays | ✓ skip weekends and listed holidays | ⚠ not mentioned in the listing | ✓ scheduler calendars |
| Cron optional, not required | ✓ | ⚠ GUI plus cron; a 2020 review hit cron for daily times | ✓ wizard, cron as an option |
| Missed-run catch-up | ✓ backfills up to 48 hours | ⚠ not mentioned | ⚠ “Fix All” for failed runs, no auto catch-up found |
| Sub-tasks / epic hierarchy | ⚠ paid plan only | ⚠ not mentioned in the listing | ✓ sub-tasks |
| Runs on Atlassian (Forge, no egress) | ✓ | ✗ | ✗ |
| Data Center / Server | ✗ | ✗ | ✓ |
| Track record | ✗ new, no reviews yet | ⚠ ~1,550 installs, 3.5★ | ✓ ~2,940 installs, 4.2★ |
Pick Encore if timezone accuracy, Forge hosting and a free plan that doesn’t end at 10 users matter more than a long review history. Pick The Scheduler if you need Data Center or Server, Automation-rule import, or the most proven option. Pick Recurring Tasks if price is the deciding factor, or you want its calendar view and JSM support, and you’ve tested its timing on your own timezone.
Where Encore fits as the alternative
Encore is built around the failures that show up in this category’s reviews:
- Each schedule has its own timezone. You pick an IANA timezone per schedule, and Encore fires at that local time through daylight-saving changes.
- Reporter set on every issue. Each created issue carries the reporter you chose.
- A run history you can check. Every run is logged as created, reopened, skipped or failed, with a reason, and a banner at the top of the Encore page lists schedules whose last run failed.
- Business days and catch-up. Schedules can skip weekends and holidays you list per project. If a run is missed, Encore backfills it within 48 hours, up to 10 issues per schedule.
- No cron required. Daily, weekly, monthly, last-day and Nth-weekday are set from a form. Cron is there if you want it.
- Make recurring from an issue. An issue action turns an existing issue into a schedule.
- Date tokens and clone mode.
{{monthYear}},{{quarter}}and similar tokens name each issue for its run date, and a schedule can clone an existing issue instead of creating a blank one.
The free plan includes all of that for up to 5 active schedules, on any site size. Standard removes the schedule limit, adds recurring epic → story → sub-task templates, and can import templates from Prefab.
The honest limits:
- Encore is new. It has no reviews yet, against hundreds of reviewed installs for the other two.
- Cloud only. No Data Center or Server.
- Fewer extras than the incumbents. No Automation-rule import like The Scheduler, and no calendar view like Recurring Tasks (Encore lists the next 14 days of runs as an agenda instead).
- Hierarchy is paid. Recurring sub-tasks or full epics need Standard.
On the Automation quota: all three apps run their own scheduler, so this isn’t a reason to choose between them. It is a reason to move off recurring Jira Automation rules, which spend your execution allowance on every run. See recurring Jira issues without Automation executions for the details.
How to try Encore
- Install Encore from the Atlassian Marketplace and open Project settings → Encore.
- Click New schedule and re-create one of your existing recurring tasks: same issue fields, cadence, time and timezone. Or open an issue and choose Make recurring.
- Check the Upcoming runs list against your current app’s next dates, then use Run now to create one issue.
- Watch the run history through one full cycle before moving the rest.
How to switch with minimal risk
- List your active schedules. Note the cadence, time, timezone, issue type and pre-filled fields of each.
- Check the deal-breakers. If you rely on Data Center, date variables, JSM requests or a calendar view, confirm the new app supports them before anything else.
- Run both for one cycle. Re-create your most important schedules in a test project and compare one full cycle against the old app, especially across a weekend or a DST change.
- Turn off the old schedule as each new one goes live, so the same issue is never created twice.
For more depth, see the full best Jira recurring issue apps comparison, recurring Jira issues on business days, and how to create recurring tasks in Jira.
If you want a recurring app that fires at the right local time and runs inside your Atlassian tenant, try Encore free with up to 5 schedules. If you need Data Center or a long track record, The Scheduler is still the safer pick.
Frequently asked questions
- Why look for an alternative to Recurring Tasks for Jira Cloud?
- It is the biggest dedicated recurring app and the cheapest of the established ones, but it is rated about 3.5 stars, and its public reviews include a 2024 report of timezone errors and older reports of the reporter field blocking saves. Teams that need issues to fire at an exact local time sometimes want a different engine.
- Why look for an alternative to The Scheduler?
- Mostly price and hosting. The Scheduler is well rated (about 4.2 stars) and feature-rich, but it costs roughly twice as much per user as Recurring Tasks, and like Recurring Tasks it is not a Runs on Atlassian app, so it can process your data outside Atlassian.
- Do these apps use my Jira Automation execution quota?
- No. Recurring Tasks, The Scheduler and Encore all run their own scheduler, so none of them consume Jira Automation executions. That only becomes a differentiator if you are comparing against recurring Automation rules.
- Is there a free alternative?
- All three are free on sites with 10 or fewer users. Encore also has a free plan on larger sites, capped at 5 active schedules, with the full single-issue engine including cron, timezones and business-day scheduling.
- When should I stay with The Scheduler or Recurring Tasks?
- Stay with The Scheduler if you need Data Center or Server, a long review history, or features like importing Jira Automation rules. Stay with Recurring Tasks if lowest price, its calendar view or its Jira Service Management support matter most.
- Can Encore clone an existing issue or use date variables?
- Yes. Encore can create a new issue, clone an existing one (copying its sub-tasks needs the Standard plan) or reopen the same issue each run, and its summary and description take date tokens such as {{date}} and {{monthYear}}. Both are on the free plan.