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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Issue getting Custom Field Opiton values via rest/api/2/issue

I am attempting to use the REST api endpoing rest/api/2/issue/<issue> to retrieve CustomFieldOption values since the api does not allow to directly pull that information in the form of a REST endpoint
When I am testing in my stage env, I can pull the metadata information via this url rest/api/2/issue/issue?expand=editmeta&fields=cf[fieldId]

This returns the complete list of values in that custom field, however when I run a similar issue in my Production the editmeta object is empty. Interestingly, when I copy the url and paste to my browser, the information pulls down fine, when I execute in my Java script or via curl the object is empty. I would like to see if you have any ideas why this may be occurring?

1 answer

1 accepted

1 vote
Answer accepted
Jens Schumacher - Released_so
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 11, 2023

Make sure that you have the necessary permissions to access the editmeta data in both environments. It's possible that the user you are using to make the API call in production does not have the necessary permissions.

Looks like you were correct, I was missing the developers role. It is working fine now

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events