-
-
Notifications
You must be signed in to change notification settings - Fork 473
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Comment (sometimes) does not add comment and returns 200 #304
Comments
Hi! Thank you for taking the time to create your first issue! Really cool to see you here for the first time. Please give us a bit of time to review it. |
@lahire you are right. This might be a bug (?) or missing optimization (?). |
I can sure try, but im too new from Go and i'm afraid of breaking your code. Because i think is not just changing the I'll try to investigate and pass it around to more go-versed peoples to see if i can learn how to adapt this |
Hey, I am very sorry that this issue has been open for a long time with no final solution. We work on this project in our spare time, and sometimes, other priorities take over. This is the typical open source dilemma. However, there is news: We are kicking off v2 of this library 🚀To provide visibility, we created the Road to v2 Milestone and calling for your feedback in #489 The development will take some time; however, I hope you can benefit from the changes. What does this mean for my issue?We will work on this issue indirectly. Final wordsThanks for using this library. |
Is really a 200 a valid response to add a comment, when the Jira Documentation states that the valid response is a 201?
https://developer.atlassian.com/cloud/jira/platform/rest/v3/#api-rest-api-3-issue-issueIdOrKey-comment-post
While it is true that 200 should be a valid response, sporadically a code im reviewing gets a 200 response but does not post anything to Jira.
Also, doing a quick search i found this weird interaction on Jira forums: https://community.developer.atlassian.com/t/rest-api-call-to-add-a-comment-on-issue-returns-200-instead-of-201/1742
go-jira/jira.go
Line 284 in 1b4556c
This is really hard to replicate, and i might be crazy, but i cannot find any reason why the Jira docs says the valid response is a 201 and not a 200.
The text was updated successfully, but these errors were encountered: