Blog · 20 September 2026

The Scheduler for Jira alternative: cost and when to switch

If you are looking for a The Scheduler for Jira alternative, it is almost always for one of two reasons: the bill above ten users, or the way scheduled issues behave once you have a lot of them. The Scheduler, by Transition Technologies PSC, is the largest app in the Jira recurring-issues category and it does the job it advertises — you define an issue template, pick how often it should be created, and Jira creates it. This page sets out what it costs today, what it gives you for that, who should simply stay on it, and where Recurring Work Items for Jira is the better fit.

The short verdict #

• Ten users or fewer? Stay where you are. The Scheduler is free at that size, and so are we. There is nothing to save by moving.
• Growing past ten users and the per-user line is the problem? That is the clearest reason to compare, and the numbers are below.
• You schedule across many projects and want one central admin screen for all of them? The Scheduler is built for that, and is the safer choice.
• You want one project's recurring work, a run history that explains every outcome, and subtasks that come with the parent? That is the shape we built for — read on.

What The Scheduler does #

Taken from the app's own Atlassian Marketplace listing, checked September 2026:

The Scheduler allows you to automate the process of creating recurring tasks in Jira. Using our add-on, you define the issue template once, select how often it should be created, and that's it!

Its listed highlights are recurring issue creation from a template, per-project management of those scheduled issues ("Manage Scheduled Issues for all the projects you're administering yourself or let other users do it for you"), and a pre-defined variable set you can drop into text fields, so a scheduled issue can carry its own creation or due date in the summary. Frequency is daily, weekly, monthly, or a custom interval, and the listing says you can use either an interval wizard or "simply use the cron expression". Access is limited to project administrators by default, with more permissions available in an Access Management settings panel.

The current cloud version at the time of writing is 7.1.0, released 16 September 2026, whose release notes add a Rovo agent for generating cron expressions and a bulk "Fix All" option for problematic fields.

That is a mature, actively maintained app. No alternative article should pretend otherwise — the question is fit and price, not quality.

What The Scheduler costs #

These are the published cloud prices for The Scheduler, read from Atlassian's Marketplace listing for the app in September 2026. Atlassian bills Marketplace apps at your Jira user tier, so the tier — not your actual headcount — is what you pay for.

Our own price is the one on our home page: free for up to 10 users, then $5.50 per user per year, which is where the right-hand column comes from. The Scheduler also publishes monthly per-user rates for larger sites — $1.00 per user per month at the 100-user tier, dropping to $0.55 at 250 users — so above a few hundred seats the gap narrows and you should price both against your own tier rather than trusting a table.

The honest summary: at ten users neither app costs anything, and between roughly 15 and 200 users The Scheduler is about twice the price of a lighter app doing the recurring half of the job. Whether that difference matters is a question about your budget, not about the software.

For completeness, the other well-known app in this category, Repeating Issues for Jira, publishes $87 at 15 users, $145 at 25, $290 at 50 and $580 at 100 (Marketplace, September 2026) — it sits between the two.

Where the two apps actually differ #

The row that decides most switches is the last two. If you are on Jira Server or Data Center, The Scheduler supports you and we do not — the comparison ends there. If you are on Cloud and your recurring work has been living in Jira Automation rules, being able to paste the export and have the rules read back is usually worth more than any per-user saving.

Who should stay with The Scheduler #

Plainly, because switching a working schedule is not free:

• You are on Jira Server or Data Center. We are Cloud-only.
• You administer recurring issues across many projects from one place. The Scheduler's cross-project management is a deliberate feature; our enrolment model is the opposite choice — a rule belongs to one project, and an unenrolled project is untouched.
• You have built a body of cron expressions you trust. They work there, and moving them is work with no user-visible reward.
• You are at ten users or fewer. There is no bill to escape.

Who should look at a lighter recurring app #

• You want scheduling scoped to one project, not visible estate-wide. Enrolment is per project and explicit.
• You need to explain a missed ticket. Every run — created, skipped or failed — is a History row carrying its reason, and the failure codes a customer can see are documented publicly rather than being support-desk knowledge.
• A recurring item is really a parent plus its steps. A rule stores an ordered subtask list, so the checklist arrives with the ticket.
• You are coming from Jira Automation and want the rules read in rather than retyped.
• The per-user line above ten users is the thing you are trying to fix.

How to switch, without a gap in coverage #

1. List what is actually scheduled. In The Scheduler, that is its per-project scheduled-issue screens; write down the frequency, the issue type and the assignee for each.
2. Install and enrol one project first. Not all of them. Pick the project with the schedules you would notice most if they stopped.
3. Recreate the rules there, using the Next runs preview to confirm each schedule reads the way you meant before you save. This is the step where time-zone assumptions surface, and it is cheaper to see them now.
4. Run both for one full cycle. A month if your schedules are monthly. Duplicate tickets for one cycle are an annoyance; a gap is an audit finding.
5. Turn off the old schedule per rule, not in bulk, and check History after the first occurrence to confirm the replacement ran.
6. Then drop the tier you no longer need. Marketplace billing follows your Jira user tier, so the saving arrives when the app is uninstalled, not when the rules stop.

If you are still deciding whether you need an app at all, our Jira recurring tasks comparison covers the free routes — Automation and cloning — and Jira Automation pricing is the honest version of when the native option stops being free.

Frequently asked #

Is The Scheduler free? Up to 10 Jira users, yes, on its published cloud prices as of September 2026. Above that it is billed at your Jira user tier, starting at $150 a year for the 15-user tier.

Can I keep using cron expressions after switching? The schedule is built in the rule editor rather than typed as cron. If you think in cron, our Jira cron expression guide explains what each field means and what cron genuinely cannot express — which is worth reading before assuming you need it.

Will my old scheduled issues disappear? Issues already created are ordinary Jira issues and stay exactly where they are, in both directions. Only the schedule stops.

Do I have to migrate everything at once? No, and you should not. Enrol one project, prove one cycle, then move the rest.

Prices and product descriptions for The Scheduler and Repeating Issues for Jira were read from their Atlassian Marketplace listings in September 2026 and can change without notice. Check the listing before budgeting.