-
-
Notifications
You must be signed in to change notification settings - Fork 876
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
search_users - allow search by query
#924
Comments
The comment suggests that the given 'username' parameter can be an email or name too. Maybe that value should just be replaced by query? This is what I'm doing here |
That would work. The only criticism would be that it’s a behavior change and could be surprising. The parameter with a default value would keep the API and behavior unchanged, but allow for using the new behavior if desired. |
Hi, I get the same problem, but can't even make the workaround to work.
On my side: |
Following #927 we now do allow a |
Should this be in the 3.0.1 version of the package? When looking at the search_users definition it doesn't have the query added. |
@mattdough this is included in the pre-release: I can see it in the documentation here https://jira.readthedocs.io/api.html#jira.client.JIRA.search_users: |
Is your feature request related to a problem? Please describe.
The
search_users
function currently only allows searching byusername
which is not supported when in strict GDPR mode. In that case, this error is returned:Currently, I don't believe there is a way around this using public functions in the library.
Describe the solution you'd like
One option would be to add a parameter such as the following to the function:
useQuery = False
. When done, thenusername
key in the params would be replaced withquery
. I think that's all that needs to be done.Describe alternatives you've considered
I can get around this problem by using the private
_fetch_pages
function:... but obviously this is gross.
The text was updated successfully, but these errors were encountered: