Page Comparison

User which will be set as reporter of new cloned issue.

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

When selected - the creator will not be notified of any changes to new cloned issue.

Summary that will be set to new cloned issue.

This field can have parameters like ${repeatingDate} - for details please follow Velocity references in field values

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 cloned 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 cloned 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)

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

Please read how to configure non-working days.

When selected - all sub-tasks from source issue will be cloned as sub-tasks to new cloned issue.

Sub-task can also have VTL expressions in summary. Just create sub-task in parent issue with summary like: "$repeating.date Sub-task template". When this sub-task will be cloned parameters will be interpolated.

When selected - all source issue links (excluding Clone link) will be cloned to new cloned issue.

When selected - all source issue attachments will be copied to new cloned issue.

When selected and Jira Agile is available - sprint field values from source issue will be also cloned to new cloned issue.

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

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