This article explains the two ways to set a custom field on the Clone + and Clone++ actions using Clone Plus for Jira App.
Instructions
To clone a custom field value to an issue, we have to use the custom field id ( or ) name in the configuration file.
Setting the custom field based on
...
customfield_id
For example: If the custom field id is 10700, then specify customfield_10700 in the configuration file .as below:
Code Block | ||||
---|---|---|---|---|
| ||||
1.set.customfield_10700 = 25/DEC/18 1.ignoreFields = customfield_10700 |
Setting the custom field based on the name
If the custom field name is short/simple then use the name as issame.
For example: If the custom field name is Rank, then use the below-mentioned code.
Code Block | ||||
---|---|---|---|---|
| ||||
1.set.Rank = "Grade-1" 1.ignoreFields = Rank |
...
If the Custom field name has multiple words in its name like, Planned delivery date then follow the below instructions:
- 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:
Code Block | ||||
---|---|---|---|---|
| ||||
1.set.Planned\ delivery\ date = 31/MAR/19 |
As a result, the date 31/MAR/19 will be set to your custom field value in the newly cloned issue.
Please see See the below image to know understand how the custom field name gets displayed in a JIRA issue.:
Ignoring the fields set on the clone plus configuration page
In order to hide the custom fields which that are already set in the clone plus configuration page form the from clone+ and clone++ custom actions we can , use ignoreFields parameter as shown below.:
Code Block | ||||
---|---|---|---|---|
| ||||
1.ignoreFields = Planned\ delivery\ date |
...