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. Required fields have a red asterisk. The form has three parts:
- Name — for your reference (not shown on created issues).
- Issue — Space and Issue type (where issues are created) and Summary (the issue's title; supports tokens, below). Any field that issue type requires appears here too.
- Schedule — frequency (daily / weekly / monthly / every N), time (pick from the list or type any time), timezone, start date, and an optional end. A live preview shows the rule in plain English.
- Details (click Show optional fields) — Description, Assignee, Reporter (defaults to the app if blank), Priority, Labels, Components, other create-screen fields including Due date (see relative dates), Subtasks, and Catch up all missed runs. When you edit a schedule that uses any of these, the section opens by itself.
Click Create schedule (bottom right). 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.
Needs attention. The list also checks each schedule's setup and flags problems before the next run fails: its space was deleted (Target shows Deleted space), its issue type is no longer available in that space, or its assignee or reporter is deactivated. A banner at the top names the affected schedules; edit the schedule to fix it, or disable it.
Who can do what
The app follows your Jira permissions. The first time each person opens it, Jira asks them to Allow access: this lets the app check what they are allowed to do, so it only offers their own spaces and fields. It's a one-time step per person.
- You can only target spaces where you can create issues. Setting an assignee needs Assign Issues; making someone else the reporter needs Modify Reporter.
- You see the schedules in spaces you can browse.
- Run now, Edit, Delete and the enable toggle are available to the schedule's creator, that space's admins, and Jira admins.
Each schedule has an owner, shown in the list: whoever created it, or whoever took it over. Permissions are checked when a schedule is saved or run manually, not on every scheduled run, so if the owner leaves or loses access the schedule keeps running as configured (the same as Jira Automation rules). The list flags owners who are Deactivated or gone (No owner). A space admin or Jira admin can then click Take ownership: they become the owner, provided their own permissions cover what the schedule does, and the change is recorded in the schedule's History.
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.
Good to know
- Issues arrive within five minutes of the time you set. Issue Repeater uses Atlassian's own scheduler, which runs every five minutes, with each Jira site given its own slot so that apps across Atlassian don't all run at once. Running on Atlassian's scheduler is what lets the app work entirely on Atlassian, so your data never leaves it. Issues are never created early and never skipped. If an issue needs to be in place by a deadline, set the time a few minutes earlier, say 8:55 for a 9:00 start.
- 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.