Unable to Insert or Update the Description Field of issue"

[Eric Thomas]

EDIT Title truncated error message

"errors":{"description":"Operation value must be an object"}} 

Pretty straight forward and followed the examples for both the creating via a post call where I got the error unless I commented out the description field values and a put call where I tried a number of things found in the boards and elsewhere.

All the documentation shows this as a string value but I am consistantly getting the above error.

Here is the data passed in the put operation that fails

{
"id" : response.id, //response from the post
"key" : response.key, //response from the post
"update" : {
"description":[{"set": "this is a description"}]
}
}

Here is the data in the post that works

{
"fields": {
"project":
{
"key":"OJ"
},
"summary":"UPDATE TEST",
"issuetype": {
"name":"Story"
}
}
}

the url I am using is the self value from the post and someone suggested adding the id and key values as above but I tried it without wiht the same results.

I am using basic auth passing my user information and the token provided in both calls and I am an administrator on the board

I am calling via google javascript 

[Andy Heinzer · Accepted solution]

Could you please let me know what specific REST endpoint you are calling here? 

Is this the v2 or v3 endpoint from our documentation?

Which specific documentation URL are you following along to?

It might just be that you're using the POST command when instead you should be using the PUT to update/edit and issue.  POST is more commonly used in the creation of data like issues, but PUT tends to be more common when editing existing fields on issues.   However without knowing the specific endpoint in use here, I don't want to make assumptions.

[Eric Thomas]

I repeated the question on the dev community and it turns out I was using v3 rather then v 2  as for the documentation url it was the REST API documentation that comes up on google searches for. Create an Issue and updating and editing an issue.  I did get it all to work but from a usability standpoint the documentation does not make a real and clear distinction between the API versions.  I think google got me here first https://developer.atlassian.com/server/jira/platform/jira-rest-api-examples/

I tried to search on how to call the V3 RTF object but I kept getting sent to the Oracle site.  This will become problematic when V2 is deprecated and w have to change our code. Currently I can not find any documentation on the subject.

Thanks for getting back I hope you can use this input to improve the documentation