If I fetch issue createmeta via REST API (/rest/api/2/issue/createmeta?projectIds=10200&issuetypeIds=10201&expand=projects.issuetypes.fields
) the options for a Select List (multiple choices) custom field (com.atlassian.jira.plugin.system.customfieldtypes:multiselect) seem to appear in random order instead of what’s been defined by the custom field.
According to one of our customers, this used to work as expected until about a month ago and since we are still using the exact same REST API endpoint, we use I assume that this must have been changed. It would be good if the allowed values would reflect the same order as defined in the custom field configuration (this seems to work for single select fields).
Below is an example of the metadata that I get from the REST API. Note that I have defined the field value order of the custom field as A, B, C, D, E in my custom field configuration.
{
...,
"customfield_10321": {
"required": false,
"schema": {
"type": "array",
"items": "option",
"custom": "com.atlassian.jira.plugin.system.customfieldtypes:multiselect",
"customId": 10321
},
"name": "Select List (multiple choices)",
"key": "customfield_10321",
"hasDefaultValue": false,
"operations": [
"add",
"set",
"remove"
],
"allowedValues": [{
"self": "https://test.atlassian.net/rest/api/2/customFieldOption/10320",
"value": "D",
"id": "10320"
},
{
"self": "https://test.atlassian.net/rest/api/2/customFieldOption/10321",
"value": "E",
"id": "10321"
},
{
"self": "https://test.atlassian.net/rest/api/2/customFieldOption/10317",
"value": "A",
"id": "10317"
},
{
"self": "https://test.atlassian.net/rest/api/2/customFieldOption/10318",
"value": "B",
"id": "10318"
},
{
"self": "https://test.atlassian.net/rest/api/2/customFieldOption/10319",
"value": "C",
"id": "10319"
}
]
},
...
}
Any chance that this can be fixed?
Cross-posting this from my DEVHELP request DEVHELP-3766