One of the major benefits of the of JCPP is the ability to customize clone operations to suit your development process. An administrator can customize these operations in the Configuration page. Before diving deep into configuring these customizations, take a look at the next section that lists all the features the app offers.
...
| Table plus |
|---|
|
| Feature | Overview | References |
|---|
| 90+ unique custom clone operations can be defined | - Name Clone operation name can be customized to reflect the purpose related to of your specific clone process
- Each operation can be enabled or disabled independently as requiredCan your needs change
- Operations allow cloned issues to be cloned to a different project or different issue type, as admin specifies
| Configuration | | Conditioning | - Each operation can have unique conditions that determine specify when the operation is available to users
- Condition - based on fields
- Condition - based on role
| Configuration | | Clone option defaults | - 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
| Configuration | | Substitution variables | Current issue fields are available as substitution variables for the setting of fields | | | Exclude field list | Use this when you do not require copying certain issue fields to the target issue even when these values are modified while cloningFields specified in this list will not be 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. | Configuration | | Ignore field list | Enable copying the Fields specified in this list will not be visible in the Clone UI display. The source value of specific issue fields this field in the original issue will be copied as-is to the target issue issue field. | Configuration | | Set fields | Use the available options in Configuration or The Configuration will provide a drop-down list of options for each set field or you can use substitution variables to define issue field values to be used while cloning | |
|
...