keelapps/Recur
For teams whose work repeats on a calendar
The work that has to happen every month, happening every month.
Weekly reports, monthly maintenance, quarterly access reviews, certificate renewals. Jira Cloud cannot create an issue on a schedule, and Automation for Jira reacts to events rather than to a calendar. Recur creates the issue on time, in the time zone you picked, and tells you exactly what it did — including the times it deliberately did nothing.
Scheduled issue creation has been asked for on Jira Cloud for years
(JRACLOUD-5185) and was closed as Won't Do. Automation for Jira
has a scheduled trigger, but no notion of what to do when the last issue it created is
still open — so the fifth unfinished monthly review looks exactly like the first.
What it does
Never pile up the same task twice
Decide per template what happens when last month's issue is still open: create it anyway, skip this round, or hold it and create it the moment the previous one closes. Every skip is recorded with its reason.
See the next ten runs before you save
The editor previews the next ten occurrences as you type, in the template's own time zone. Nothing about the schedule is left to be discovered later.
Time zones that survive daylight saving
09:00 stays 09:00 across the switch. Monthly on the 31st falls back to the last day of shorter months — 28 February, or the 29th in a leap year.
“Why was there no issue” always has an answer
Every run is accounted for in the history: the issue it created, or the reason it did not. A skip is a recorded result, never a silent absence.
Assignees that rotate
Walk a list in order and wrap around, so the same person is not on the hook every time. Deactivated members are skipped rather than assigned.
Runs entirely on Atlassian infrastructure
Built on Forge. No external servers, no data leaving Atlassian, nothing extra for your vendor security review to look at.
A monthly maintenance check, end to end
-
Build the issue once
Issue type, summary, description, assignee.
{{date}}and{{n}}fill themselves in, so TLS renewal check #4 numbers itself. -
Pick the cadence and the time zone
Every N days, weeks on chosen weekdays, months on a date, or months on the nth weekday — first Monday, last Friday.
-
Say what happens if the last one is still open
Create anyway, skip, or wait for it to close. Per template, not per site.
-
Check the preview, then save
Ten dated runs, in the template's own time zone, before the template exists. From then on the history shows what each one did.
Against what you have today
| Question | Native Jira | Recur |
|---|---|---|
| Create an issue every month on the 31st? | Not supported | Yes |
| Monthly on the 31st, in February? | Not supported | Last day |
| Stay at 09:00 across a daylight saving change? | Not supported | Yes |
| Skip this month because last month is still open? | Not supported | Per template |
| Why was no issue created on Monday? | Not recorded | In the history |
| Which recurring tasks exist across the whole site? | Not supported | Admin page |
Availability
Recur is live on the Atlassian Marketplace. It is built and deployed on Atlassian Forge and installs into your Jira Cloud site straight from the listing.
Licensing is handled by Atlassian. Sites with 10 users or fewer are free with every feature; paid tiers start above that.
Questions, bug reports and feature requests: raise a support request.
Found a security issue? Please report it privately rather than in a public channel.