Hey there,
I am updating the all of my API endpoints to v3 and noticed something that was not expected when creating a comment. In the documentation the the add Comment endpoint the different for both API versions:
V2
body
string
The comment.
V3
body
anything
The comment.
When I assign the body field as a string using the V2 API it works all good. When I assignee the body field as a string in V3 I get the following error:
{"errorMessages":[],"errors":{"comment":"Comment body is not valid!"}}
Has something changed that the API document is not outlining?
Cheers, Phil
This problem was solved? I´m in the same situation right now.
Yes having same problem, found the docs here for v3:
https://developer.atlassian.com/cloud/jira/platform/rest/v3/#api-rest-api-3-issue-issueIdOrKey-comment-post
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Also seems like the JSON payload returned for get issue has changed in V3. The description field is nested without other fields:
V2
"description": "example bug report",
V3
"description": { "type": "doc", "version": 1, "content": [ { "type": "paragraph", "content": [ { "type": "text", "text": "example bug report" } ] } ] },
Is there any reference to these changes?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you. This solved my problem.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.