Versions Compared

Old Version 14

changes.mady.by.user Sireesha Dugginapeddi [Appfire] (Inactive) (Deactivated)

Saved on

compared with

New Version 15

changes.mady.by.user Nishanth Thimmareddy

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Summary

One of the major benefits 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 provides an overview of each customization feature.

...

Table plus
autoNumbertrue


FeatureOverviewReferences
90+ unique custom clone operations can be defined
  • 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
Configuration
Conditioning
  • Each operation can have unique conditions that specify when the operation is available to users
  • Condition based on fields
    • project
    • issue type
    • status
    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

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.

Configuration

Ignore field list

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.


Configuration

Set fieldsThe Configuration provides 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.


...