Recurring Tasks for Jira

Auto-create Jira issues on a daily, weekly, or monthly schedule.

Runs on Atlassian

What it does

Jira has no built-in way to create issues on a repeating schedule — so teams fake it with reminders, calendar events, or copy-paste. Recurring Tasks adds the missing capability: define a rule (an issue template plus a cadence) once, and the matching issues are created automatically, on time, in your timezone. Ideal for weekly reports, daily standups, monthly maintenance, quarterly access reviews, and renewal reminders.

Getting started

Install from the Atlassian Marketplace, then open Apps → Recurring Tasks in Jira.
Click New rule and choose the project and issue type to create.
Fill in the issue template: summary (tip: use {{date}} to insert the run date), description, assignee and reporter (searchable people-pickers), priority, components, labels, and an optional due date ("N days after creation").
Set the cadence — daily, weekly, or monthly, with "every N" (e.g. fortnightly) and, for weekly, one or more weekdays. Pick the time of day in your own timezone.
Save. The issue is now created automatically on schedule. Use Run now to create one immediately and confirm it looks right.

Useful options

Dynamic dates: {{date}}, {{date+7}}, {{date-1}} in the summary or description insert the run date (and offsets) — e.g. Weekly report {{date}}.
Skip if the previous issue is still open — avoids piling up duplicates.
Stop after a date to auto-end a rule.
Run history on every rule shows exactly what was created, when, and any errors.

FAQ

Can't Jira already do this?: No — native Jira has no recurring-issue feature. This adds it.
Does it handle timezones and daylight saving?: Yes. You pick the time in your local timezone and it stays correct across DST changes.
What permissions does it need?: Read Jira work data and users (to build the issue), and create issues. It runs entirely on Atlassian Forge with no external data egress.
Where is my data stored?: Your rules are stored in Atlassian Forge storage, inside your installation's boundary. Nothing leaves Atlassian.