How to create a monthly recurring task in Jira

Monthly jobs are everywhere in Jira — the end-of-month report, the first-of-the-month access review, the recurring maintenance window — and every one of them is the same small chore: someone remembers (or doesn’t) to recreate the issue, on the right day, every month. Jira has no “repeat monthly” switch. Your real options are recreating the issue by hand, building a scheduled Automation for Jira rule (which spends your automation execution allowance and fights month-end math), or scheduling it once with a recurring-issues app like Cadence that handles month-end, business days and timezones for you. Here’s how to make a task that genuinely recurs each month.

Why Jira can’t do it on its own

Jira tracks issues; it doesn’t schedule them. There’s no field that says “create this again next month,” which leaves three options:

• By hand — recreate the issue each month. Reliable only while someone remembers, and the details drift each time.
• Jira Automation — a scheduled trigger can create an issue, but you hard-code the issue inside the rule, every run spends from your automation execution allowance (counted by individual step rather than by run from 3 December 2026), and the trickier timings (month-end, business days) are awkward to express.
• A recurring-issues app — purpose-built for exactly this.

The parts that trip people up

Monthly recurrence sounds simple until the calendar gets involved:

• Month-end — “the last day” is the 28th, 30th or 31st depending on the month. A fixed “the 31st” silently misfires in February.
• Business days — “the first business day of the month” has to skip weekends (and ideally holidays), not just land on the 1st.
• Timezone and DST — “9am on the 1st” should mean 9am locally, every month, including across daylight-saving changes.

Get these wrong and your “monthly” task lands on the wrong day — or not at all.

The fix: a schedule that handles the calendar for you

Cadence creates the issue on your monthly schedule and gets the edge cases right:

• Flexible monthly rules — a fixed date, the last day of the month, the Nth weekday, or the first business day, handled correctly across months of different lengths.
• Timezone-aware, DST-correct — each schedule runs in its own timezone, so the time you pick is the time it fires all year.
• A run history — see that each month’s issue was created (or why one was skipped), instead of hoping.
• No automation budget — recurrence doesn’t draw on your Jira Automation execution allowance. See recurring Jira issues without automation executions for why that matters at scale.

The takeaway

Jira has no native monthly recurrence, and the DIY routes either rely on memory or make you fight the calendar inside an automation rule. Set the schedule once — month-end, business-day and timezone handled — and the monthly issue just shows up, consistent and on time. For the broader how-to see how to create recurring tasks in Jira, and for weekend/holiday handling see recurring Jira issues on business days.