Summary
...
| Info |
|---|
This is the documentation for Clone Plus for Jira Cloud. If you using Clone Plus for Jira Sever/Data Center, refer the Customization Information - Server page. |
One of the major benefits of Clone Plus for Jira is the ability to customize clone operations to suit your development process. An administrator can customize these operations in on the Configuration page. Before diving deep into configuring these customizations, take a look at the next section that provides an overview of each customization feature.
Features
...
| autoNumber | true |
|---|
...
- Clone operation name can be customized to reflect the purpose of your specific clone process
- Each operation can be enabled or disabled independently as your needs change
- Operations allow cloned issues to be cloned to a different project or different issue type, as admin specifies
...
- Each operation can have unique conditions that specify when the operation is available to users
- Condition based on fields
- project
- issue type
- status
...
...
- Set default options
- Options available
copy attachments
copy watchers
copy comments
copy subtasks
- copy subtask estimates
copy estimates
copy parent versions
copy links
- copy epic issues
- copy epic issue subtasks
- copy epic issue subtask estimates
- copy worklogs
...
Current issue fields are available as substitution variables for the setting of fields
...
...
Fields specified in this list are not cloned over from the original issue to the target issue, even if they are added or edited while cloning. The values are cleared in the newly cloned issue.
...
...
Fields specified in this list are not visible in the Clone UI display. The source value of this field in the original issue is copied as-is to the target issue field.
| Note |
|---|
This is not applicable to subtask(s) cloning. |
...
...
For more details, refer the following pages:
| Child pages (Children Display) | ||
|---|---|---|
|