For Jira Cloud · Built on Forge
Monthly compliance tasks. Quarterly reviews. The 2nd Tuesday. The last business day of the month. Native Jira stops at "every 2 weeks" — this doesn't.
No automation quota used · runs entirely on Atlassian infrastructure
The whole reason this exists
Jira's built-in "Set to recur" caps out at two weeks. Anything monthly or longer means hand-built automation — cron expressions and smart-value conditions that work, but spend your automation execution quota and scatter across a rule apiece.
What you get
Monthly, quarterly, annual, every-N-weeks, and Nth-weekday — including "last day of the month."
Each schedule carries a full template — summary, description, fields, and a subtask checklist — generated every cycle.
Targets that land on a Saturday roll forward to Monday. No more tasks appearing on days nobody works.
Generate the issue a few days early so the work is queued and ready before it's actually due.
Runs on its own Forge scheduled trigger — it never touches your Jira automation execution quota.
Built on Forge. Your data never leaves Atlassian's infrastructure — nothing to host, nothing to breach.
Three steps
Choose the project, issue type, and build the template with subtasks and fields.
Monthly on the last day, quarterly, the 2nd Tuesday — whatever the real schedule is.
Every day the app checks what's due and creates it. You just do the work.
Pricing
Billed by Atlassian, on your existing Jira invoice. No separate signup.
Questions
Not natively. Jira's built-in "Set to recur" only offers daily, weekly, every weekday, and every two weeks — there's no monthly, quarterly, or annual option. That gap is exactly why this app exists.
Yes — it's a first-class option. Native Jira can't do the 2nd Tuesday at all; automation can, via a TUE#2 cron, but Recurring Issues does it with no cron and no automation quota.
Every schedule can carry a template with subtasks and prefilled fields, so the entire checklist is regenerated on cadence — not just a single issue.
No. It runs on its own Atlassian Forge scheduled trigger, completely separate from Jira automation, so your execution limits are untouched.
Entirely inside Atlassian. The app is built on Forge and stores schedules in Atlassian's hosted storage — nothing is sent to an external server.
Ready
Install from the Atlassian Marketplace and create your first schedule in minutes.
Find Recurring Issues on the Atlassian Marketplace