-
-
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
User.Find impossible to use correctly #385
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. |
The problem is that Jira Cloud API accepts |
I used this to write my own request for 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. |
Describe the bug
I wanted to use an accounts key to find out the account id, by calling
client.User.Find("ntr0")
but I only got thiserror getting user data for account id ntr0: The username query parameter was not provided: request failed. Please analyze the request body for more details. Status code: 400
Expected behavior
I get a list of users with matching usernames.
Possible Solution
I think the short solution would be to replace the "query" arg with the desired "username" arg.
go-jira/user.go
Line 238 in a1f44bd
It should also be possible to provide a User.GetByKey and User.GetByUsername methods would be really nice to have, since these would only return a single user with exact matching key or username.
Your Environment
Additional context
The text was updated successfully, but these errors were encountered: