-
-
Notifications
You must be signed in to change notification settings - Fork 456
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
Calling the GetWatchers() function results in a stacktrace #634
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
What did you expect to happen?
GetWatchers() succeeds and doesn't panic.
How can we reproduce it (as minimally and precisely as possible)?
I don't know if there is an easy way to reproduce the panic. One thing to try is to simply call GetWatchers() on an issue that has watchers. The returned list will be empty because the Watchers api no longer returns an AccountID for each Watcher and now returns a Key and a Username
Anything else we need to know?
Your Environment
Include as many relevant details about the environment you experienced the problem in
go-jira version (git tag or sha): this is actually seen with 1.16.0 but also can be reproduced with 2.0.0 (top-of-tree commit ID 2e11dff)
Go version (
go version
): go1.19.9Jira type (cloud or on-premise): on-premise
Jira version / Api version: 2
The text was updated successfully, but these errors were encountered: