Scheduling Clone Issue action

Setup task details

Go to issue view.
Find and click Repeating - Manage in the details pane on the right.
Click Edit button (pencil icon).
On the form select Clone Issue as repeat action and configure further details and recurrence schedule.
When finish, then click Repeat Issue button.

Configuration fields for Clone Issue action

Field name	Description

Field name	Description
Reporter	User which will be set as reporter of new cloned issue. 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 cloned issue.
Remove me from watchers	When selected - the owner will not be added to watching list of new cloned issue and will not be notified of any changes. 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 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: 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) 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 cloned issue created date and due date. Please read how to configure non-working days..
Sprint value	Defines how to set the sprint value in new cloned issue. Possible values: `Clone from source issue` - sprint value will be copied from source issue `Assign to accivt sprint` - sprint value will be set to the first active sprint matching the sprint name specified in Sprint name field `Assign to future sprint` - sprint value will be set to the first future sprint matching the sprint name specified in Sprint name field `Put in backlog` - sprint value will be empty
Sprint name	Used in selection of correct active or future sprint. The first sprint whose name contains this text will be selected for new cloned issue. The field can also be empty, which will select the first active or future sprint regardless of its name. The specified sprint name may also contain velocity template language expressions. Sample values: `$sourceIssue.project sprint` - assuming the task is configured in project with key DEMO, sprint whose name contains “DEMO sprint” will be matched, e.g: “DEMO sprint”, “DEMO sprint 2”, “Next DEMO sprint” `Sprint iter` - it will match sprints whose name contains “Sprint iter”, e.g: “Sprint iteration 1”
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 velocity template language 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.
Notify watchers	When selected - watchers of new cloned 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

After clicking "Choose fields to edit..." user can add more system and custom fields defined in Jira that will be updated during task execution. Each field will have simple form input where static value or dynamic value can be provided - see Velocity expressions in field values.