The 4-step wizard
From Quick Start, select More options to carry the fields you have entered into the full wizard. Use it for settings beyond the one-screen form, including descriptions, holiday calendars, end rules, sub-tasks, and sprints. Make this issue recurring on a Jira issue opens Quick Start with supported fields filled in; select More options there to reach the wizard.
Steps: What, When, Rules, Review. Use Back and Next; Save is on the last step. Cancel or Back to the list leaves without saving.
1. What
| Field | Notes |
|—|—|
| Schedule name | Required. Shown in the list. |
| Project | Required. Cannot be changed after saving: create a new schedule instead. |
| Create | Only in a Jira Service Management service project: Jira issue (default) or Service request. See Service requests. |
| Issue type | Required. Loaded from the chosen project. For a service request, Request type replaces it (name and portal description). |
| Summary | Required. One line, 255 characters at most. Supports variables. |
| Description | Rich text, written with a small toolbar or simple marks: **bold**, _italic_, ~~strike~~, `code`, [text](https://...), # heading, - list, 1. list, - [ ] checklist (a Jira checklist), > quote, and code blocks between three backticks. A blank line starts a new paragraph. A preview below the field shows the description as Jira will show it. Supports variables anywhere in the text. Content the editor cannot edit (tables, panels, images, mentions, emojis, colours), for example from an issue you made recurring, appears as a placeholder such as ⟦kept 1: table⟧: it is kept as is and shown read-only in the preview (“Some content can’t be edited here and is kept as is”). Deleting or changing the placeholder removes that content (the editor warns you); typing the same text does not create one. A backslash is always plain text. A copied description you do not edit is saved exactly as it is in the issue; once you edit it, empty paragraphs are removed. Mentions notify the person every time an issue is created, so the preview warns about them. Up to 32,767 visible characters. |
| Assignee | Project default (Jira’s default assignee for the project, unassigned if the project has none), the schedule owner (you), a specific user who can be assigned issues in the project, or Rotate between people: an ordered list of 2 to 20 such users. Each new issue goes to the next person in the list, then back to the first. The turn follows the occurrence number ({{number}}): skipped occurrences still use up their turn, editing the list applies from the next occurrence by its number, and Run now goes to the person of the next planned occurrence. Review and the schedule page show the order and who is next. If a saved person can no longer be assigned, the wizard warns you and Jira refuses that issue. With Project default, RepeatWise leaves the assignee to Jira: if the project assigns new issues to its lead, the lead gets them. |
| Priority | Optional. Default: the project default. |
| Labels | Separate with commas or spaces. |
| Additional fields | Collapsed by default. Components, fix versions (unreleased only), parent (search by summary or key), and the due date as a number of days after the occurrence date (negative for days before). Leave a field blank to not set it. Custom fields: the issue type’s required custom fields are always listed and must be filled; add optional ones with Add a field. Text, paragraph, number, date, single and multi select, and user fields are supported. A date field (for example Start date) can be a fixed date or N days after the occurrence date. Text fields accept the summary variables. Changing the project or issue type clears them. |
Also link each new issue to KEY (only when you started from Make this issue recurring): each new issue gets a Relates link to the source issue, added right after the issue is created. If the link fails (for example issue linking is turned off), the issue is kept and the run shows a warning; a retry never adds the link twice. Attachments are not copied. An issue with an issue security level cannot be copied or linked to: a schedule is visible to everyone who can see its project.
For a service request, the step shows the summary, description, and priority, labels and due date when the request type has them, with the note “Sub-tasks, sprints and custom fields are not available for service requests”. Required request fields RepeatWise cannot fill block the save with a clear message.
You can add and reorder sub-task templates, each with a summary, optional description (same editor) and assignee choice. RepeatWise creates them under each new issue, in order. See Chaining, sprints and sub-tasks. Custom fields have no wizard controls. If the project requires one, saving is blocked with a message asking you to make it optional or give it a default in Jira.
2. When
Frequency, repeat interval, time, time zone, start date, end, and how many days early to create. See Frequencies, Time zones and Early creation.
End options: Never, After a number of occurrences, On a date (inclusive). “After N occurrences” counts the first N dates the rule produces, including dates that are skipped by a holiday policy.
3. Rules
Holiday calendar (country, optional region, extra and removed days) and the policy when a date falls on a weekend or holiday. You can also choose what happens to the previous issue if it is still open, and a board with sprints to add new issues to, with a fallback when no sprint is active. Service requests are never added to a sprint. See Holidays and Chaining, sprints and sub-tasks.
4. Review
- A summary sentence of the schedule.
- Next 10 occurrences: when each issue is created, its due date, and a note when the date differs from the plain rule (holiday move, clock change, last day of month, and so on). Times are in the schedule’s time zone.
- The issue that will be created, with variables filled in for the first occurrence.
- Skip and Move actions for a single previewed occurrence, plus an exception list with Undo.
- If the rule is invalid, or no issue would ever be created, the step says so and explains why.