Chaining, sprints and sub-tasks

These options are set in the wizard and applied every time RepeatWise creates an issue. They all run as the schedule owner.

Previous issue

In Rules, choose what to do if the previous issue is still open. The previous issue is the last issue RepeatWise created for this schedule. An issue in a “Done” status category is closed. Any other status counts as open.

The comment and the transition are never sent twice for one occurrence.

If the previous issue was deleted or the owner cannot see it, the new issue is created anyway, with a warning. If Jira rejects the comment or the transition, for example because the transition is no longer allowed, the new issue is kept and the occurrence log shows a warning. See Errors.

Sprint

In Rules, pick a board with sprints. This works with Scrum boards and with team-managed boards that have sprints turned on. Kanban boards, and team-managed boards with sprints turned off, have no sprints.

RepeatWise adds each new issue to the active sprint of the board. If several sprints are active, it uses the one that started first. If no sprint is active, your choice applies:

If the board or sprint cannot be found, or the owner cannot add issues to it, the new issue is kept and the occurrence log shows a warning. Sub-tasks follow their parent issue.

Sub-tasks

What lets you add and reorder sub-task templates. Each has a summary, an optional description and an assignee choice of Project default (Jira’s default assignee for the project, unassigned if the project has none) or schedule owner. Variables can be used in the text.

RepeatWise creates the sub-tasks under each new issue, in the order you set. It uses the sub-task issue type of the project. If a sub-task fails, RepeatWise retries it, and it searches Jira first so that no sub-task is created twice. If it still fails after the retries, the new issue and the sub-tasks already created are kept, the occurrence log shows the reason, and the schedule goes to Error.

Not available

Parent issues, components, fix versions and custom fields are set under Additional fields on the first step (see The wizard). Sub-tasks do not get the parent’s custom fields. Service requests have no sub-tasks, sprint or custom fields; the previous-request rules work as for issues.