Options for Select List (multiple choices) appear in seemingly random order in issue createmeta

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

Hello @tbinna, we’ve met same problem. I’ve created an issue here :upside_down_face:

Ah that’s good to know, thanks @AlanLeszczuk! It’s a shame that there doesn’t seem much intention to actually fix this (based on the comments on the issue).

We have more and more customers complaining on this issue. I am wondering if you have found any workaround at least.

@tbinna did you confirm whether it has worked before?

@maciej.dudziak unfortunately not. My bug report is unattended since Oct 25 :frowning_face: and there is not much moving on @AlanLeszczuk’s one either. I am not sure what’s the best way to grab Atlassian’s attention these days but I guess the best we can do is keep commenting on that issue.

Yeah, unfortunately we are losing customers because of something that seems to be easly fixed. We have just received a ticket from another customer, which is on trial and whether he buys a license is determined by an ability to fix the issue

We’ll engage with the Jira Cloud ecosystem team to see what’s going on here.

EDIT: https://ecosystem.atlassian.net/browse/ACJIRA-2003 – pinging the Jira Cloud ecosystem team for more info.

2 Likes

For those of you not following ACJIRA-2003, but are interested, please head over here to monitor progress: https://ecosystem.atlassian.net/browse/ACJIRA-2003

@BeataSzturemska from the Jira Cloud ecosystem team just commented 5 hours ago that there’s a fix that’s going to be put in place, and has asked if anyone wants to have a feature flag flipped on their dev/test instances in advance of this being rolled out into production.