Versions Compared

Old Version 3

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

Saved on

compared with

New Version 4

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

Saved on

Key

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


Div
idProductTOC

On this page

Table of Contents
maxLevel1
excludeOn this page
typeflat
separatorpipe

Summary

One of the major benefits of the JCPP is the ability to customize clone operationsactions to suit your development process. This capability has been provided since the initial version of the plugin. Since version 3.x, we have made it possible to provide very sophisticated customization capabilities without programming. It still requires a clear understanding of your JIRA system and processes, but, the implementation can be done via a property-based configuration with average JIRA administration knowledge and some careful testing. Open an issue if you need more extensive customization than what is currently provided.An admin 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.

Features

Table plus
autoNumbertrue


FeatureOverviewExamplesReferences
Up to 16 unique clone As many as unique custom clone operations 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

  • 1.label = Escalate to Engineering

  • 1.tooltip = Creates a task for Engineering

  • 2.label = Create a Requirement


Conditioning
  • Each can have unique conditions that determine when the action is available
  • Generic on condition fields
  • Condition-based on fields
    • project
    • issue type
    • status
  • Condition-based on role
1.condition.ZCLONE.*.* = true

  • 2.condition.*.*.1 = true

    • 1-plus.role.ZCLONE = Developers

    Clone properties 

    Clone option defaults
    • Set default options
    • Options available

      • copy attachments

      • copy watchers

      • copy comments

      • copy subtasks

      • copy estimates

      • copy parent versions

      • copy links

      • copy epic issues (since 6.5)
      • copy epic issue subtasks (since 6.5)
      • copy epic issue subtask estimates (since 6.5)
  • option.copyLinks = true
    • 1.option.copyAttachments = false
    Substitution variables

    Current issue fields are available as substitution variables for the setting of fields

    1.set.summary = BLOCKER: %original_summary%

    Exclude field list to prevent copying to clone

    In many use cases, certain fields should not be copied to the target issue

    1.fieldExcludes = custom2, custom three

    Clone properties

    Ignore field list for fields that should not be show on clone screen

    Control fields that are allowed to be changed by the user during the clone operation1.ignoreFields = Special

    Clone properties

    		Mapping fields from original issue to a new value in the target issue conditioned on original issue field values

  • Map to a new project based on the project, issue type, and status

  • Map to a new project based on project and component

    • Map to a new type based on the project, issue type, and status

  • Map to a new component based on the component name

  • Map to a new version based on the version name

    • 1.project.SUPPORT.*.* = ENG

    • 1.component.UI = User interface

    Clone properties

    Setting standard and custom fields

    1.set.description = Some standard description


    Get started

    ...


    Additional information

    Child pages (Children Display)