The work that comes back, handled

Every team has work that repeats. The backup check every Monday. The invoice run on the last working day of the month. The access review every quarter. Jira has no way to create any of it on its own, so somebody has to remember, and eventually somebody does not.

Routine creates those issues for you, on the right day, in the right timezone, without anyone learning cron.

Schedules people actually ask for

Every two weeks. The first Tuesday of the month. Working days only. The last working day of the month. Written in plain English, chosen with one click.

Month ends that behave

A rule set for the 31st lands on the 30th in a 30 day month, and on the 28th or 29th in February. It never slides into the next month.

Timezones that are right

Each rule runs on its own timezone and its own hour. Daylight saving, teams spread across the world, none of it moves your issue to the wrong day.

Never twice

A rule creates at most one issue per day, whatever the platform does underneath. Duplicate tickets are not a thing your team has to clean up.

Written for the person reading it later

Put {{monthName}} or {{date}} in the summary and it is filled in on the day, so "Invoice run {{monthName}} {{year}}" arrives as "Invoice run August 2026". Add subtasks, a due date a few days out, labels, components and an assignee, and the issue lands ready to work on rather than ready to be edited.

Honest about the clock

At or after your chosen hour, never before it. Atlassian runs scheduled app code in batches rather than at an exact second, so we promise the day and the hour rather than the minute. We would rather say that here than have you discover it later.

Private by design

Your data never leaves Atlassian. Routine runs entirely on Atlassian Forge and declares no external permissions at all, so it cannot call any outside service even by accident. No analytics, no tracking, and no AI processing of your issues. It creates the issues your rules describe and never touches anything else.

Under control

Only Jira administrators can create or see rules, using Jira's own permission check. Every rule shows its next run date, its full history, and why any run failed. Skip a single occurrence without deleting anything, pause a rule, or duplicate one to build the next.

Pricing

Free for teams up to 10 people. Above that, one low flat price per user with everything included, billed by Atlassian on your existing invoice.

Get support