Recurring Jira issues with sub-tasks, sprints, and previous-issue rules

RepeatWise can create ordered sub-task templates under each recurring issue and add the new issue to a board’s active sprint. In the same schedule, you can decide what happens when the previous issue is still open.

Configure the issue and its follow-up work

  1. Open RepeatWise, select New schedule, then More options. In the wizard’s What step, choose the project and issue type, enter the parent issue summary, and add sub-task templates in the order you want them created. Each sub-task needs a summary; description and assignee choice are optional. The project needs a sub-task issue type.
  2. In When, set the frequency, time, time zone and start date for the recurring issue.
  3. In Rules, choose a board with sprints. Scrum boards and team-managed boards with sprints enabled are supported. RepeatWise adds each new issue to an active sprint; if more than one is active, it chooses the one that started first. Sub-tasks follow their parent issue.
  4. Choose the fallback for a date with no active sprint: leave the issue in the Backlog, or use the Next planned sprint. If there is no planned sprint, the issue stays in the backlog.
  5. Still in Rules, choose what to do if the previous issue is open: Create anyway, Skip this occurrence, Create and comment on the previous one, or Create and move the previous one to a status. The last option needs a workflow transition that is allowed from the previous issue’s current status. With the comment option, RepeatWise adds the comment “Next occurrence created: KEY-123” to the previous issue, where KEY-123 is the new issue.
  6. In Review, check the next 10 occurrences and example issue, then select Save.

FAQ

Will this work on a Kanban or team-managed board without sprints?

No. Choose a Scrum board or a team-managed board with sprints turned on for sprint assignment. See Chaining, sprints and sub-tasks.

What counts as an open previous issue?

The previous issue is the last one RepeatWise created for that schedule. A Jira status outside the Done category counts as open.

What happens if a sprint or sub-task step fails?

If sprint assignment fails, the new issue remains and the occurrence log shows a warning. If a sub-task still fails after retries, the new issue and any completed sub-tasks remain, and the schedule enters Error; see Errors and what they mean.

For the basic setup, see How to create recurring issues in Jira Cloud and The 4-step wizard.