Public REST API to manage custom field options


Currently it's not possible to add, remove or view options of custom fields via the REST API. The only way is to use the UI.

Anyone that has permissions to do it in the UI, should also be able to do it using a set of new REST API endpoints.




Tomasz Zasada
December 9, 2020, 5:25 PM

Hi Everyone!

We’ve recently published new Jira APIs for custom field options management.
These brand new APIs support custom field options in both global and project-specific contexts.
It’s a full set of APIs to read, create, update, delete and reorder custom field options:


Thomas Opiolka - codefortynine
July 23, 2020, 12:06 PM

We would also benefit from this API endpoint.

From our point of view the ability to enable and disable field options would even be more important than simply deleting them. Currently, when you delete a field option, all relations on issues where that option was selected previously are lost. Disabling a field option would prevent this and keep at least the relations intact. Do you have any plans on adding those?

A list of field options that changes frequently also needs a way to rank them. Otherwise, you will end up with a well-sorted list at the beginning (from the first sync), followed by a randomly sorted appended list. Maybe an automated ranking after adding or updating field options would also do the trick here.

Mateusz Szerszynski
January 30, 2020, 12:57 PM

And any plans expanding it to other contexts also?

It's one of the possible future enhancements, it's tracked separately in

Margus Nael
January 30, 2020, 10:06 AM

Sry for confusion did not notice that there is a separate section for apps - did not expect that since it wasnt there for some time ago…

Margus Nael
January 30, 2020, 9:54 AM

Ok. Thus its not the issue for expanding the feature to “custom fields created by apps”. Currently the sad thing is that connect apps can create select list custom fields but cant manage their options. Its only allowed for jira:

Note that this operation only works for issue field select list options created in Jira or using operations from the Issue custom field options resource, it cannot be used with issue field select list options created by Connect apps.

Any plans to allow apps to work with options?


And any plans expanding it to other contexts also?


Only options from the global context are returned.






Krzysztof Kercz