Documentation
Using Issue Repeater for Jira
Auto-create recurring Jira issues and subtasks from reusable templates.
Opening the app
In Jira, open the left sidebar → Apps → Issue Repeater. You land on the schedule list.
Creating a schedule
Click New schedule and fill in:
- Name — for your reference (not shown on created issues).
- Project and Issue type — where issues are created.
- Summary — the created issue's title. Supports tokens (below).
- Description, Assignee, Reporter, Priority, Labels, Components — optional standard fields. Reporter defaults to the app if left blank.
- Other fields — remaining create-screen fields, including custom fields and Due date (see relative dates).
- Subtasks — an optional list of subtask summaries, created under each issue.
- Recurrence — frequency (daily / weekly / monthly / every-N), time, timezone, start date, and an optional end.
Click Create schedule. Nothing is created until the schedule is enabled and its first occurrence is due.
Template tokens
Use these in the summary or description; they resolve per occurrence in the schedule's timezone:
| Token | Expands to |
|---|---|
{{date}} | Occurrence date, e.g. 2026-07-01 |
{{datetime}} | Date and time, e.g. 2026-07-01 09:00 |
{{week}} | ISO week number |
{{month}} | Month name, e.g. July |
Relative due dates
For Due date (and any date field), prefer "N days after creation" over a fixed date — a fixed calendar date in a recurring template goes stale and is immediately overdue. Relative dates are recomputed fresh on every occurrence. A fixed-date option is available for the rare case you need it.
Managing schedules
From the list, each schedule shows its target, recurrence, next due time, and Last run status.
- Run now — create an issue immediately from the template (handy for testing).
- History — a run log with status, timestamps, and links to every created issue.
- Edit — change anything; the next due time recomputes.
- Enable toggle — turn a schedule on or off without deleting it.
- Delete — stops future creation. Issues already created are unaffected.
Reliability
- Never miss: if the app was paused or a run was delayed, the engine catches up the occurrences that became due (by default the most recent one; switch on "Catch up all missed runs" per schedule for full back-fill).
- Never duplicate: each occurrence creates exactly one issue, even under retries.
- Visible failures: if a run errors, the schedule shows Last run = Error and the History view has the details.
Notes & limits
- Timing is honoured to within ~5 minutes, not to the exact second. This is a property of the Atlassian platform, not a design choice: apps that run on Atlassian use Atlassian's scheduler, which operates on a fixed 5-minute cycle. It's the direct trade-off for no data leaving Atlassian — apps that fire to the exact second do so by running on their own external servers, which means your Jira data is sent off-platform. The engine never fires early and never misses, so the worst case is a few minutes late.
- Issues are created by the app (the Creator/audit field); the visible Reporter and Assignee are whoever you choose.
- A few uncommon field types (e.g. cascading selects) aren't supported yet; if one is required on an issue type, you'll see a clear message and can pick another type.
Questions? support@runsonlabs.com.