You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I use Postman to test a PUT request in my JIRA sandbox.
My JSON body:
{ "update": {"customfield_15315": [{"set":"11111011112"}]}}
but keep on getting the following response:
{ "errorMessages": [], "errors": { "customfield_15315": "Field 'customfield_15315' cannot be set. It is not on the appropriate screen, or unknown." }}
I essentially just want to edit one field on the issue. I get this error on all the field, custom and standard.
I have admin rights and the field is visible the create/view/edit screens of this project.
This is my path rest/api/2/issue/464382 with no parameters set
That syntax is correct. When you say it's visible, can you please confirm that if you try to create/edit an issue through the UI, you can actually see the field you want to populate?
Thanks,
Kian
Hi Kian,
Thanks for the reply.
I can see the field on my create & view screen.
What bothers me is if I run the following GET request https://jira.stage.eu-west-1.aws.clickatell.com/rest/api/2/issue/464382/editmeta
I only get this response: { "fields": {}}
I was under the impression that the response should list all fields available.
When I run this GET request https://jira.stage.eu-west-1.aws.clickatell.com/rest/api/2/issue/464382/?
I get a response with all fields on that issue, even the fields that are not visible on the screen.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Any other ideas in regards to what I can look out for?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@David van Staden,
That is odd, as that URL works for me if I want to look at the edit meta in my instance. Are you having problems with other API's, or just these ones?
Thanks,
Kian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.