Clone properties



Getting Started

Start with Getting started with customization before diving into the details here.


The clone property file allows customized control over clone operations. This page describes how specific behaviors can be controlled. This page focuses on conditioning and control. See Setting fields for information on generally updating field values.

Property files are lines of key/value pairs that map keys to values - see property file syntax. The keys recognized by clone operations are defined below.

Mapping Keys

Mappings keys are dot-separated property names: prefix.class.qualifier1.qualifier2.qualifier3.

  • prefix - this is the profilePrefix or blank (default prefix) from the clone action

  • class - determines what mapping is being defined - like project, type, etc...

  • qualifier(s)

    • one or more (dot separated) qualifiers - the number of qualifiers is dependent on the class

    • generic qualifier (*) matches any value of that position

More specific keys take precedence over more generic keys during lookup 

If you use names, make sure you escape blanks in names using \ as required by property file syntax.


1.project.JRA.1.* will match an issue in the JRA project with has type bug (1) in any (*) status



  • UI conditions apply to custom actions only, not base actions. Custom actions will not show unless at least 1 condition property is defined and not false.

  • For issue type configurations, the following are different scenarios of displaying the target issue type in the Clone window while cloning an issue:

    • When the original issue type exists in the target project, it is displayed in the window.

    • When the original issue type does not exist in the target project, the default issue type of the target project is displayed.

    • When the original issue type does not exist in the target project and default issue type is not configured in the target project, one of the available issue types from the target project is displayed.

Other properties


Comma separated values

  • Double quotes for entries in values that need a comma separated lists are removed. 

  • Double quote names containing a comma.

Property file syntax

The clone property file follows standard property file format with some extensions and some clone specific conventions

  1. Standard property file syntax as defined by Java summarized by:

    • comment lines start with # or !

    • key value pairs with syntax like key = value

    • keys are separated from the value by a separator that is one of =, :, or blank

    • \ is the the standard escape character, use \\ if you need the \ character

    • blanks or other special characters within a key must be escaped

    • lines can be continued by escaping the line terminator - this means having a \ at the end of a line just before the line terminator

  2. For Clone Plus for JIRA release 2.2.0 and above, an Apache commons extension is supported summarized by:
    properties can reference other properties

    1 1.fieldExcludes = ${fieldExcludes}, "some other field"


  3. Clone specific conventions