One of the major benefits of the JCPP is the ability to customize clone actions to suit your development process. An administrator can customize these actions 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 |
|---|
| Unlimited 90+ unique custom clone actions 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 to a different project or different issue type
| Configuration | | Conditioning | - Each can have unique conditions that determine when the action is available
- Generic on condition fields
- 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 to prevent copying to cloneIn many use cases, certain fields should not be copied | Use this when you do not require copying certain issue fields to the target issue | Configuration | | Ignore field list for fields that should not be show on clone screenControl fields that are allowed to be changed by the user during the clone operation | Enable copying the source value of specific issue fields to the target issue even when these values are modified while cloning | Configuration | | Set fields | Allow the clone action applicable to only the specified values for:
- Project
- Issue types
- Status
- Role
| Configuration |
|