Recurring Issues for Jira — Documentation

Last updated: 19 August 2026.

Recurring Issues lets you attach an Outlook-style repeat schedule to a Jira issue. Once a schedule is set, the app automatically creates a new issue on that cadence — daily, weekly or monthly — so recurring work such as status reports, reviews and maintenance tasks does not have to be re-created by hand.

Requirements

• Jira Cloud. The app is a Forge app and does not run on Server or Data Center.
• Permission to create issues in the target project — the app creates issues as the app itself, so the app must be able to create the chosen issue type in the chosen project.
• The person saving a rule needs the Create Issues permission in the target project; the app verifies this at save time.
• No external accounts, API keys or configuration are needed.

Installation

1. Install the app from the Atlassian Marketplace, or from within Jira via Settings → Apps → Manage apps → Find new apps and search for "Recurring Issues".
2. Confirm the requested permissions and complete the install.
3. Open any issue — the panel appears without further setup.

Where to find it

The app adds an issue panel called Recurring Issues. Open any Jira issue and scroll to the panel section of the issue view; the panel is titled "Recurring issue". There is no global or project-level admin screen — everything is configured per issue.

Using Recurring Issues

1. Open the issue you want to use as the template and find the Recurring Issues panel.
2. Fill in Issue summary, Project key (for example PROJ) and Issue type (for example Task). These are the values each newly created issue will get.
3. Pick a Frequency: Daily, Weekly or Monthly.
   • Weekly: choose how many weeks between runs and which weekdays.
   • Monthly: choose either a day of the month (1–31), or a weekday pattern such as "the first and third Monday". If the selected day of the month does not exist in a given month, the last day of that month is used.
4. Enter a Time as HH:MM in your local time. It is converted to UTC before being saved.
5. Check the Summary line — it restates your settings in plain English, for example "Every 2 weeks on Monday and Thursday".
6. Press Save. The panel then shows an Active badge with the next scheduled run.

From then on it is automatic. A daily scheduled trigger runs in the background, finds every rule whose next run has passed, creates the issue, and calculates the next run date. Press Delete in the panel to stop a schedule.

Limitations

• Forge offers no cron scheduling, only fixed intervals. The trigger runs once a day and Atlassian controls the exact moment it fires, so an issue is created on the correct day but not at the exact minute you entered. The time of day determines the schedule maths, not the precise delivery time.
• Times are stored in UTC using the offset that applied when you saved the rule; the app has no daylight-saving handling, so a rule saved in summer may shift by an hour in winter.
• Created issues carry only a summary, project and issue type. Description, assignee, priority, labels, components and custom fields are not copied from the template issue.
• When you save a rule, the app checks with Jira that you personally hold the Create Issues permission in the project you named, and refuses to save if you do not. It does not validate the issue type; a wrong issue type is only discovered when the daily trigger runs, and the failure is written to the app log and retried on the next run.
• Rules saved before version 4.0 carry no authorisation record. The daily trigger refuses those rules until someone opens the panel and saves them again, which re-runs the permission check.
• One rule per issue. Deleting the Jira issue itself does not delete its rule — remove the rule from the panel before deleting the issue.
• The panel does not list all rules across the site; each rule is visible only on the issue it is attached to.

Support

Questions, bug reports and feature requests: info@kyc-checks.nl. We aim to reply within two business days.