Managing Clone Issue action options
Basics
To manage Clone Issue action options please go to Apps → Manage your apps → (Repeating Issues app) Settings → Clone Issue task tab.
Clone Issue options
Some option have "Enabled" and "Allow override by user" toggles:
Enabled - when marked, given option is enabled by default to all repeated tasks
Allow override by user - when marked, the user who creates the repeated task will see this option in the form when configure the task and can decide whether this option should be enabled for this single repeating (e.g. even if the option is enabled by default, user can disable option for single configuration)
Option | Description |
|---|---|
Issue link type | The name of issue link type that will be used to create links between original issue and cloned issue by the Repeating Issues app. Empty value means that no links will be created between issues. |
Summary | Summary field template (see https://codedoers.atlassian.net/wiki/spaces/PRIC/pages/2913140744 ) that will be used when setup new Clone Issue action |
Clone subtasks | When enabled - subtasks from source issue will be cloned as sub-tasks to new cloned issue. |
Clone links | When enabled - source issue links 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. |
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. |