Versions Compared
compared with
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Setup repeating details
- Go to issue view .
- Select More > Repeat from issue action navigation bar or click Set repeating in Repeating Issue section on the right panels.
- On repeating configuration dialog please select Clone Issue for repeat action field.
Configuration fields for Clone Issue action
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 Available variables in repeating action param strings | ||
Repeat for | Define which issue date should be repeated: issue create date or issue due date. For example, if issue duration is 2 days, and the repeating occurence falls on 10 January 2017then:
| ||
Issue duration | The number of working days between new cloned issue created date and due date. Please read how to configure non-working days. | ||
Notify watchers | When selected - watchers of new created issue will be notified via email. See Email notifications. | ||
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 parameters in summary. Just create sub-task in parent issue with summary like: "${repeatingDate} 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 sprint values | When selected and Jira Agile is available - sprint field values from source issue will be also cloned to new cloned issue. |
On this page
Table of Contents |
---|