One of the major benefits of the 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 can be customized to reflect the purpose related to your process
- Each can be enabled independently as required
- Choose either
- clone to the same project and issue type
clone Can be cloned to a different project or different issue type
| Configuration | | Conditioning | - Each can have unique conditions that determine when the operation is available
- 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 issueissue even when these values are modified while cloning | Configuration | | Ignore field list | Enable copying the source value of specific issue fields to the target issue even when these values are modified while cloningissue | Configuration | | Set fields | Allow the clone operation applicable to only the specified values for:
- Project
- Issue types
- Status
- Role
| ConfigurationUse the available options in Configuration or substitution variables to define issue field values to be used while cloning | |
|