Managing Clone Issue action options

Basics

To manage Clone Issue action options please go to Jira Administration > System > Issues > (Repeating Issues) Clone Issue action

Some option have "Status" and "Allow override by user" values:

Status - when marked, given option is enabled by default to all repeatings
Allow override by user - when marked, the user who creates the repeating will see this option in the form when configure the repeating and can decide whether this option is enabled for this single repeating (e.g. even if the option is enabled by default, user can disable option for single configuration)

'-' value means that given option can be enabled only by administrator and user can't be allowed to override this option.

Option	Description

Option	Description
Summary	Summary field template (see https://codedoers.atlassian.net/wiki/spaces/PRI/pages/548241460) that will be used when setup new Clone Issue action
Clone sub-tasks	When enabled - sub-tasks from source issue will be cloned as sub-tasks to new cloned issue.
Clone links	When enabled - source issue links (excluding Clone link) will be cloned to new cloned issue.
Clone attachments	When enabled - source issue attachments will be copied to new cloned issue.
Clone watchers	When enabled - source issue watchers will be cloned to new cloned issue. Watchers will receive notifications. Note that watchers will be cloned only when the repeating had been setup by user who has 'Manage watcher list' permission in the project. Please read the Jira documentation - Managing project permissions on how to edit permissions.
Clone archived version values	When enabled - source issue archived versions (for Fix Version and Affected Version field) will be cloned to new cloned issue.
Clone released version values	When enabled - source issue released versions (for Fix Version and Affected Version field) will be cloned to new cloned issue.
Clone sprint values	When enabled - sprint field values from source issue will be also cloned to new cloned issue.