There are two ways to set a custom field in Clone plus This article explains two different ways of setting a custom field value on the Clone + and Clone++ actions using Clone Plus for Jira.

Instructions

To clone a custom field value to an issue, we have to use the custom field id ( or ) name in the configuration file. How to use a custom field-id

Set the custom field based on custom field id

For example: If the custom field id is 10700, specify customfield_10700 in the configuration file , please use the below mentioned code.as below:

1.set.customfield_10700 = 25/DEC/18
1.ignoreFields = customfield_10700

otherwise

If the requirement is to use Custom field name and if it has multiple words in its name like (Planned delivery date) then follow the below instructions:

Need to escape each and every space character with a '\ ' only when the custom field name has multiple words along with a space(s) character(s) in it.

...

Set the custom field based on the custom field name

If the custom field name is short/simple, use the same.

For example: If the custom field name is Rank, then use the code mentioned below"

1.set.Rank = "Grade-1"
1.ignoreFields = Rank

If the Custom field name has multiple words like, Planned delivery date, you need to escape each space character of field name with '\ ' (backslash and space).

Example for Clone+ (custom1) operation so, we have to set the command with prefix '1'. 

...

in the configuration page:

1.set.Planned\ delivery\ date = 31/MAR/19

As a result, the date 31/MAR/19 will be set to your custom field

...

in the newly cloned issue.

...

See the below image to understand how the custom field name gets displayed in a JIRA issue:

Image Added

Ignore the fields set on the clone plus configuration page

In order to hide the custom fields that are already set in the clone plus configuration page from clone+ and clone++ custom actions, use the ignoreFields parameter as shown below:

1.ignoreFields = Planned\ delivery\ date

...

Please see the below image to know how the custom field name gets display in a Jira issue.

Image Removed

Note: Following are some of the acceptable Custom field names with our app, so you may use these formats in the name, i.e. custom-multi-select, custom_cascade_select, custom\ three, custom-date-type-field etc...

Date Format: Any JIRA application property format should work.