Update issue field option

[Abhishek Biyani]

It seems Jira cloud API allows to update an option for a select list issue field via PUT /rest/api/3/field/{fieldKey}/option/{optionId} and if the option does not exist, a new option is created.

However, it is not allowed for Jira server. Also, if we import a csv in Jira server and map a column to select list field, a new option is created, if the option does not exist.

Why is this behaviour not consistent?

[AhmadDanial]

Hi there, Abhishek.

A quick answer to this would be the fact that they are technically different products. While JIRA Cloud is constantly being shipped with the latest update, JIRA Server functionality may not have it / behave similarly.

We can compare this from the explanation provided in the official documentation:

• Cloud: Updates an option for a select list issue field. If the option does not exist, a new option is created as you have mentioned above.
• Server: You only have the ability to POST (to create a custom field) and GET (to return the information for system and custom fields)

In general, this was discussed in the following thread last year when comparing the differences between the REST API behavior:

• Difference between Jira Cloud REST API and Server REST API?