Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Not able to add an option to a NextGen field using REST API

I am trying to use the REST API to add an option to a NextGen Drop Down field.

I have attempted to use /rest/api/3/customField/13173/option, but I get a 400 response with a message: b'{"errorMessages":["Global context does not exist for the field 13173."],"errors":{}}' 

How can I determine what ContextID I need to use for this specific NextGen project?

1 answer

1 accepted

0 votes
Answer accepted
Prince Nyeche Community Leader Dec 22, 2020

Hi @David Frager 

Welcome to Community! Not all Jira Cloud API would work on a next-gen project, such as customField option, this exist on classic projects as next-gen doesn't have a way yet to modify individual fieldset except you're calling this from a connect app. then you can use the connect app API for customfield options. Likewise each field on a next-gen project is Project based and not Global. 

@Prince Nyeche Thanks for the reply.  

Am I able to write a connect app to interface with our cloud instance of JIRA?

We have several critical data fields used by Classic JIRA that I need access to in a nextgen project.  Since this is not possible, and the data does not change frequently, my plan was to write a quick application to do a compare / merge to keep these fields updated for both types of projects.   If the connect app API solves that, then I can investigate that path.  

Prince Nyeche Community Leader Dec 22, 2020

Hi @David Frager 

Just to reiterate, next-gen fields are completely separate entities from Classic fields. So if in your use case, you created similar custom field (bearing the same name or not), then you can do a comparison / update the next-gen field with the Classic field data. And Yes you can interface with a connect app, but you probably have to go through this docs to understand JWT and how you can use it. Read this article on issue fields to get more context.

Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Published in Jira

Announcing the waitlist for Jira Work Management

Hey there Cloud Community members! We’re excited to give you the first glimpse of the new home for business teams on Jira — Jira Work Management. Jira Work Management is the next generation of J...

876 views 14 20
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you