Documentation
Install Recurring Issues for Jira from the Atlassian Marketplace onto your Jira Cloud site. It is a Forge app, so there is nothing to host and no external service to configure — installation is the whole setup.
You need Jira administrator permission to install it. Once installed, the app appears in your Jira apps menu.
Open Apps in the Jira navigation and choose Recurring Issues. Every schedule across your site is managed from this single page — there is no per-project configuration to hunt through.
A schedule has three parts: where issues go, what they look like, and when they are created.
Choose the project and the issue type the schedule creates. Every issue this schedule generates lands in that project as that type.
The template is what each generated issue is filled in with:
Monthly compliance review.A schedule can also create subtasks beneath each generated issue. Give each subtask a summary and, optionally, a description. They are created under the parent issue automatically, so a recurring checklist arrives already broken down.
These are the patterns the app supports. The last four are the ones native Jira automation cannot express directly.
| Type | What you set | Example |
|---|---|---|
| Daily | Nothing | Every day |
| Weekly | One or more weekdays | Every Monday and Thursday |
| Every N weeks | An anchor date and an interval | Every 2 weeks from 5 Jan 2026 |
| Monthly by date | A day of the month, 1–31, or last | The 15th, or the last day of the month |
| Monthly by Nth weekday | An occurrence and a weekday | The 2nd Tuesday of every month |
| Quarterly | A starting month and a day | The 1st, every 3 months from January |
| Annually | A month and a day | Every 1 April |
Short months. A monthly by date schedule set to a day that does not exist in a given month simply does not fire that month — day 31 produces nothing in February, April, June, September, or November. If what you want is month-end, set the day to last instead. That correctly resolves to the 28th, 29th, 30th, or 31st as appropriate.
Two options control what happens when a scheduled date lands on a non-working day.
With this on, no issue is ever created on a Saturday or Sunday. Instead the app rolls forward: a target date that falls on a weekend produces its issue on the next business day. A month-end schedule landing on a Saturday creates its issue on the following Monday rather than being silently dropped.
Provide a list of dates to treat the same way as weekends, one per line in YYYY-MM-DD form:
2026-12-252027-01-01Holidays roll forward exactly like weekends, and the two combine — a target landing on a holiday that is followed by a weekend rolls past all of them to the next working day.
Set create in advance to give your team lead time. A schedule with a lead time of 3 days creates its issue three days before the date it is scheduled for, so the work is visible in the backlog before it is due rather than on the morning it is needed.
Leave it at 0 to create issues on the scheduled date itself.
Every schedule is either active or paused. Pausing stops issue creation without losing the configuration, which is the right move for a schedule you expect to resume — a seasonal process, or one on hold pending a decision. Paused schedules are skipped entirely on each daily run.
Editing a schedule affects future issues only. Issues already created are ordinary Jira issues and are never modified or removed by the app. Deleting a schedule likewise leaves everything it has already created untouched.
The app evaluates every active schedule once per day on a scheduled trigger. There is no CRON to maintain and no automation-rule quota consumed.
Dates are evaluated in UTC. Recurrence is calculated against the UTC calendar day, not your local timezone. If you are well behind or ahead of UTC, an issue may appear on what is locally the adjacent day. This is deliberate: it keeps schedules stable and predictable rather than shifting with daylight saving.
The app is paid via Atlassian, and there is a free tier for small teams. On sites without an active licence the daily run does not create issues. Active trials count as licensed, so everything works normally during an evaluation.
If the admin page shows a licence-inactive state, check your subscription in Manage apps in Jira.
The app requests three scopes:
Schedules are stored in Atlassian's Forge storage inside your own environment. The app runs entirely on Forge with no external egress: no third-party servers, no analytics, nothing to breach elsewhere. Uninstalling removes the app's stored configuration. See the privacy policy for the full detail.
Work through these in order:
31 does not fire in a 30-day month — use last for month-end.create in advance the issue appears earlier than the scheduled date.Schedules are evaluated on the UTC calendar day — see when schedules run.
The template's assignee is optional. If it is empty, the project's own default assignment applies.
Open a support request and include your Jira site URL, the project involved, the schedule's recurrence settings, and what you expected to happen. See the support page for more.