There are two ways to set a custom field in Clone plus for Jira.
...
To clone a custom field to an issue, we have to use the custom field id (or) name in the configuration file. How to use a custom field-id in the configuration file, please use the below mentioned code.
For example: If the custom field id is 10700, then specify customfield_10700 in the configuration file.
Code Block | ||||
---|---|---|---|---|
| ||||
1.set.customfield_10700 = 25/DEC/18 1.ignoreFields = customfield_10700 |
otherwise
If the requirement is to use Custom field name and if it or
If the custom field name is short/simple then you can use the name as is. 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 |
otherwise
If the Custom field name has multiple words in its name like (, Planned delivery date) then follow the below instructions:
...
Here we are providing this example for Clone+ (custom1) operation so, we have to set the command with prefix '1'.
Include the below code in configuration page.
Code Block language xml theme Midnight 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.
To not to display your custom field in the cloning screen, then please include the below statement along with above code.
Code Block language xml theme Midnight 1.ignoreFields = Planned\ delivery\ date
Please see the below image to know how the custom field name gets display in a Jira issue.
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.
...