-
Suggestion
-
Resolution: Unresolved
-
None
-
135
-
41
-
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
It would be nice to be able to deal with custom fields using Jira REST API.
At the moment, it's possible to get some info by retrieving editmeta :
http://example.com:8080/jira/rest/api/2/issue/{issueIdOrKey}/editmeta
But you cannot add, edit, or delete custom fields via JIRA REST API (as you can in the admin section).
Workaround
- The third party plugin Jira Customfield Editor provides REST endpoints for the CRUD operations on custom fields.
- There is a possibility to add new custom field by using the following REST method: https://docs.atlassian.com/software/jira/docs/api/REST/8.22.0/#field-createCustomField
- relates to
-
- Closed
-
- Closed
-
- Gathering Interest
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
-
-
-
-
-
-
[JRASERVER-28539] Add, edit, or delete custom fields in REST API
Tried editing custom field with below rest api. Not sure we have this support available in Jira cloud.
Any leads will be highly appreciated.
/rest/api/3/issue/{issueIdOrKey}?notifyUsers=false
I vote for this too, as we are also looking for adding/updating custom field in jira using REST API. Just curious, why this ticket has been not been resolved for so long?
Hey all!
My name is Hanna, I'm a designer working on Jira. We're currently exploring ways to improve the experience for administrators to clean up custom fields. To provide a better solution for our customers we are researching the usage of System Jira and external 3rd party apps custom fields.
If you'd like to participate in this research and run 3 SQL scripts on your Jira instance that will show the number of system and external custom field configurations without any sensitive data and send the report back to us, please drop me a line - hsazonava@atlassian.com.
I will share all the details via email.
Thanks and looking forward to hearing from you,
Hanna.
Here's my scenario: Someone added a custom field with bad characters in the values or description. This causes the fields admin page not to load. I want to update the field desc/values via REST, but can't. As a result I have to poke around in the database, which Atlassian says I should not do.
We could also really use this. Our scenario:
We have a custom field which currently has just under 5,000 options.
Every month, we need to add 5-10 more, which I do via ScriptRunner import.
I can easily see in SQL which options have never been used, and would love to delete them, but...
It takes a full 3 minutes and 40 seconds to delete an option.
Yes, I did time it: That's a little over 1 minute to reach the confirmation page, 2 minutes to delete the option, and 30 seconds or so to load the field config page in Chrome.
Thus, I am the only person who ever even tries to do this, because the pain is simply too great.
If we had an API, then I would have an easy way to both add and remove options as needed, and this field would be around 1500 options total, as there'd be a reasonable way to maintain it.
The Affects Version should be updated to include 8.X now as well. 
Our updates recently have been lagging behind because we have to rely on a 3rd party plugin that does not update on the same schedule.
When will this be resolved? When need to delete old values in a custom field in version 9.4 Data Center!