Can Jira create an issue on the last business day of the month?

Native 'Set to recur' can't — it has no monthly option and no concept of a business day. Jira automation can, using the {{now.lastBusinessDayOfMonth}} smart value in a scheduled rule's condition, or a dedicated recurrence app that does it in one setting without spending automation quota.

How do I skip weekends for a recurring Jira issue?

In automation, use business-day smart values like lastBusinessDayOfMonth or toBusinessDayBackwards. In a recurrence app like Recurring Issues for Jira, turn on 'skip weekends' and any target landing on a Saturday or Sunday rolls to the previous business day automatically.

Recurring Jira issues on the last business day of the month

UPDATED 2026 · 5 MIN READ

Month-end close. Financial reporting. Payroll cutoff. A whole category of operational work is due on the last business day of the month — specifically the last business day, because it can't land on a weekend. Here's how to schedule it in Jira Cloud, and the honest tradeoffs of each route.

Native "Set to recur" can't

No monthly recurrence. Native tops out at every 2 weeks, so "the last day of the month" isn't on the menu.
No concept of a business day. Even if it could do monthly, it has nothing to keep a task off a weekend.

Jira automation can — with a business-day smart value

Automation has a dedicated smart value for exactly this: {{now.lastBusinessDayOfMonth}}. The usual pattern is a scheduled trigger that runs daily, with a condition that only fires on the right day:

Scheduled trigger: daily · Condition: {{now.format("yyyy-MM-dd")}} equals {{now.lastBusinessDayOfMonth.format("yyyy-MM-dd")}}

Because lastBusinessDayOfMonth already accounts for weekends, you don't hand-roll the date math. So automation genuinely does this — the cost is in how it does it.

What the automation route costs

Daily polling against your quota. To catch one day a month, the rule runs every day and checks the condition — ~30 executions a month, against your plan's automation limit, to create one issue.
Smart-value literacy. Someone has to know lastBusinessDayOfMonth, toBusinessDayBackwards, and the formatting functions — and maintain them.
Per-rule sprawl. Every recurring task is its own rule, with no single place to see them all.

The two-toggle way

Recurring Issues for Jira treats "last business day" as a setting, not a smart-value condition — and runs on its own Forge trigger, so it spends zero automation quota:

Open the Recurring Issues page and click New schedule.
Pick the project, issue type, and a template — add subtasks for the close checklist if you want the whole runbook generated.
Set the recurrence to Monthly and enter last for the day.
Turn on Skip weekends. If month-end lands on a Saturday or Sunday, the issue rolls to the preceding Friday.
Optionally set a create-in-advance lead time so the checklist appears a few days early.

Where "last business day" work shows up

Finance — month-end close, accruals, reconciliations, reporting.
Payroll & HR — cutoff and approval deadlines.
Ops & compliance — monthly sign-offs, access reviews, KPI submissions.

Which should you use?

Comfortable maintaining a daily-polling rule with smart-value conditions? Automation works. Want it as a two-toggle setup that costs no automation quota and lives in one management page — especially for finance-critical work you can't afford to have drift — that's what Recurring Issues is for.

Add Recurring Issues to Jira — free for up to 10 users

Next: where Jira automation works and where it breaks → · Back to the full guide