nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

What field types are compatible with api/2/field/{fieldKey}/option endpoints?

JP Rowan

I am trying to create a select field that I can update the options using the rest API. There are a complete set of endpoints designed for this purpose, yet when I attempt a GET call on any of my select fields I am returned the following error:

{
  "errorMessages": [
    "The field with the given key does not exist or does not support options"
  ],
  "errors": {}
}

I have attempted creating a new field using the POST /rest/api/2/field method with the following definition:

{
    "name": "New Customer Field",
    "description": "Custom field for picking groups",
    "type": "com.atlassian.jira.plugin.system.customfieldtypes:select"
}

and still I am returned the same error above when I attempt to use any of the /option endpoints. Can someone please explain what field type are the endpoints designed to work with?

Screen Shot 2016-12-14 at 8.21.40 AM.png

Accepted answers

JP Rowan

For clarification, this endpoint is only compatible with fields that are created with an Atlassian Connect Add-on. Currently there is no support for editing select field values via API for Cloud instances.

All comments

Volodymyr Krupach @BrizoIT

Checked this in my cloud instance and got the same error. Please report a bug: https://confluence.atlassian.com/support/atlassian-cloud-bug-fixing-policy-206865884.html

Noah Van Loen

+1 – Did a bug get logged for this error?

JP Rowan

I have a ticket in with the support team, but I was informed this is expected behavior due to the fact this endpoint was intended to only work for fields created by a Connect Add-on. I was then pointed to this site: https://developer.atlassian.com/ to submit feedback, but when I submitted the form I got this error:

Screen Shot 2016-12-14 at 8.21.40 AM.png

I am now waiting on support to create the feature request for me...

Volodymyr Krupach @BrizoIT

Hi JP Rowan,

Thank you for sharing the status!

Eli Evans

As far as I can tell, you can create an empty custom field, but there are no ways to add values to the custom field using REST. My successful postman body for creating an empty select list was

{

"name": "Whatever",

"description": "Custom field for whatever",

"type": "com.atlassian.jira.plugin.system.customfieldtypes:select"

}

I was not able to post/put any options, nor do anything effective with options at creation. Hoping to get some resolution to this. There has been at least one ticket open for this for over a year sad

https://jira.atlassian.com/browse/JRA-36112 Hopefully we can restart the campaign.

Eli Evans

From today's support ticket I was told to sit and wait and hope something gets done in that feature request. I'm following up to see if I can expose those API points myself by writing a rest plugin, but that is a little beyond me and I hope it does not come to that.

Volodymyr Krupach @BrizoIT

Hi Eli,

You can not expose own REST for JIRA cloud. It's possible only for JIRA Server.

Eli Evans

Thank you for the definitive answer, it has been difficult finding anything concrete for what can and cannot be done with so many versions of JIRA running around.

Tien Hoang_zlqfpb

Do we have any update on this this issue, i also have the same problem with my Jira cloud ?

JP Rowan

Jira Implementaton

is it resolved?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

jira-core