Recurring Jira issues that know your calendar.
Schedule on real business days, skip public holidays, and stop creating the next issue when the last one is still open. No cron. Preview every run before you save.
The next 5 runs are computed and shown before a schedule is saved. Click to enlarge.
No cron, ever
Plain-English rules like Last business day of the month. Never a five-field expression.
Business days & holidays
US, UK, DE, AU, JP, KR and more — including lunar and substitute holidays. Bundled, no lookups.
No duplicate open issues
Skip the next occurrence until the previous one is resolved. Your backlog stays honest.
Timezone & DST safe
Each schedule fires at the wall-clock time you set, in the timezone you pick — correct across DST.
The difference is the calendar — and knowing when not to create.
Automation can create an issue on a schedule. It cannot ask whether today is a business day, whether the holiday moved, or whether last month's issue is still sitting in your backlog.
| Capability | Jira Automation | Schedloop |
|---|---|---|
| Recurring issue creation | Yes | Yes |
| “Last business day of the month” | —Not supported | Yes |
| Skip public / lunar / substitute holidays | —Not supported | Yes |
| Skip while the previous issue is still open | —Not supported | Yes |
| Preview the next runs before saving | —Not supported | Yes |
What teams put on a loop
Three schedules that break the moment a holiday or an unfinished ticket gets involved.
Month-end close
Finance needs the checklist on the last business day — not the 31st, not a Sunday.
09:00 America/New_York
Holiday calendar: US
On-call handoff
A weekly handoff issue that doesn't pile up when the previous rotation never closed theirs.
08:30 local to the schedule
Skip while previous is open
Quarterly access review
Compliance work that has to land on a working day in every region it touches.
10:00 Asia/Seoul
Lunar + substitute holidays
There is no server of ours to review.
Schedloop is a Forge app in the Runs on Atlassian program: it makes no external network calls, holds no external secrets, and stores nothing outside your own Jira site.
Read the full privacy policyQuestions admins ask first
Can't I do this with Jira Automation?
You can create issues on a schedule. You can't express “last business day of the month”, skip a holiday that moved to a substitute day, or hold the next occurrence until the previous issue is resolved — those need calendar and state awareness Automation doesn't have.
It's a new app. What am I trusting?
Less than usual. Schedloop runs entirely on Atlassian Forge with no servers, no egress, and no external secrets — so there is no vendor infrastructure between you and your Jira site. Everything it stores is visible and deletable from the app's settings page.
Will our security team pass it?
The review is short: four Jira scopes, Forge-hosted storage, zero outbound network calls, and Atlassian-managed auth and data residency. Send them the privacy policy — it lists every scope and every stored field.
What happens to our data if we uninstall?
Forge removes the app's storage as part of the platform uninstall lifecycle. Individual schedules can be deleted any time from the settings page.
Does it handle timezones and daylight saving?
Each schedule fires at the wall-clock time you set in the timezone you choose, so 09:00 stays 09:00 on both sides of a DST change.
What does it cost?
There's a free tier to start, and billing (if you move to a paid plan) is handled by Atlassian on your existing account — no separate contract or card.