-
-
Notifications
You must be signed in to change notification settings - Fork 469
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
Cannot read jira.Response body #468
Comments
In case of an error, go-jira reads and decodes the response body and returns it as an |
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. |
Describe the bug
I am abstracting the process of transitioning a Jira issue to a different state. When attempting to transition an issue from
Backlog
toReady
, the Jira web app raises an error telling me I need to define the story points. I'd like to handle this error when automating the process. I have the following function:I am trying to read the response body if there is an error transitioning the issue. But I get the following error when trying to do so:
How can I read the error response from the API?
Expected behavior
The
jira.Response
returned fromDoTransition
should be readable.Your Environment
Include as many relevant details about the environment you experienced the problem in
v1.15.1
go version
):1.18.3
8.13.11
Additional context
I'd like to be able to dynamically handle error responses that come from the API. Or at least be able to print a more helpful error message when a request to transition the issue fails.
Thanks!
The text was updated successfully, but these errors were encountered: