Page Comparison

...

Field name

Description

Reporter

User which will be set as reporter of new subtask issue in parent issue.

Info
This is not the creator of new issue. The creator of new issue will be the app user Repeating Issues App.

Assignee

User which will be set as assignee of new subtask issue.

Remove me from watchers

When selected - the owner will not be added to watching list of new subtask issue and will not be notified of any changes.

Info
Owner is the user who configure the task. This field is only visible if watching is enabled. This option is set in General configuration for Jira. See Configuring Jira application options for details.

Summary

Summary that will be set to new subtask issue.

This field can have parameters like $repeating.date - for details please follow Velocity references in field values

Repeat for

Defines which date field of issue should be repeated accordingly with recurrence rule: the create date or the due date.

For example, if issue duration is 2 days, and the repeating occurrence falls on 10 January 2017 (based on recurrence rule) then:

when issue create date is selected - new subtask issue will be created at 10 January 2017 with due date equal 12 January 2017 (due date is calculated to be 2 days after 10 January 2017)
when issue due date is selected - new subtask issue will be created at 8 January 2017 with due date equal 10 January 2017 (create date is calculated to be 2 days before 10 January 2017)

Info
Issue create date and issue due date is calculated with non-working days adherence. For details read Managing non-working days

Issue duration

The number of working days between new subtask issue created date and due date.

Issue Subtask issue type

Issue type of new created subtask.

Notify watchers

When selected - watchers of parent issue will be notified via email. See Email notifications.

Mute success notifications

When selected - notifications of correct execution will not be sent. See Email notifications.

...

Versions Compared