Setup repeating details
...
| Field name | Description | ||
|---|---|---|---|
| Reporter | User which will be set as reporter of new cloned issue.
| ||
| Assignee | User which will be set as assignee of new cloned issue. | ||
| Remove me from watchers | When selected - the creator will not be notified of any changes to new cloned issue.
| ||
| Summary | 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 | ||
| 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:
| ||
| Issue duration | The number of working days between new cloned issue created date and due date. Please read how to configure non-working days. | ||
| Clone sub-tasks | 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. | ||
| Clone links | When selected - all source issue links (excluding Clone link) will be cloned to new cloned issue. | ||
| Clone attachments | When selected - all source issue attachments will be copied to new cloned issue. | ||
| Clone sprint values | When selected and Jira Agile is available - sprint field values from source issue will be also cloned to new cloned issue. | ||
| Notify watchers | When selected - watchers of new created 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. |
Other system and custom fields
...