Step-Free Scheduler for Jira

Recurring issues, reminders and digests — without building them out of automation rules.

Jira still has no recurring issues

JRACLOUD-5185 has been open since 2005. If you need a ticket every Monday, a review on the last working day of the month, or a nudge on everything that has not moved in a fortnight, you are building it out of automation rules — or remembering to do it by hand.

Three kinds of job

Create an issue

One new issue from a template, every time the schedule fires.

Comment on issues matching a filter

A nudge, a reminder or a follow-up on everything a JQL filter matches.

Summarise a filter into one issue

A digest listing what matched. However many issues matched, it is one run and one issue — which is the whole difference from an automation rule that loops over each of them and is charged per iteration.

The daylight-saving part, which is the part that usually breaks

Most tools in this category store the next run as a moment in time and add twenty-four hours. That is not "tomorrow": on the night the clocks change, a local day is 23 or 25 hours long, so a 09:00 job quietly starts running at 08:00 and stays there for six months.

Here a schedule is a local time in a named timezone, and the moment is worked out from the calendar every single time. When the clocks go forward and the time you chose does not exist, your job runs at the first minute that does — or skips that day, if you prefer. When they go back and the time happens twice, it runs once. Both are marked in the run history, so an unusual timestamp explains itself.

You see the next five runs before you save

The editor shows what the schedule will actually do, worked out by the same engine that runs it. It is where you find out that "the 31st" skips February, before you save it rather than six months later when an issue you were counting on did not appear.

Honest about the timing

Jobs are dispatched hourly. A job set for 09:00 runs during the 09:00 hour, not at 09:00:00. That is the finest interval the Forge platform offers, and we would rather say so here than let you discover it. There is a Run now button so you never have to wait a week to find out whether a weekly job works.

Each job stays inside one project

A job names one Jira project and can only ever write there. You prove you can do that thing in that project when you save the job: if you cannot do it by hand, the app will not do it for you on a timer. Everything it writes says which job produced it and who set it up.

Nothing leaves your site

Runs on Atlassian. Compute and storage inside Atlassian's infrastructure, no external connections, verified by Atlassian's own eligibility check. Details in the privacy policy.