Hi !
We have a workflow that does the following:
1- query the user infos of a certain email address (example; https://ID.atlassian.net/rest/api/2/user/search?username=name.lastname@ID.com)
2- Parse the response and put the accountID into a variable
3- Use that variable to create an issue.
Now all this doesn't work anymore cause if the error: error "The query parameter 'username' is not supported in GDPR strict mode". The configuration in Global Admin > General Settings for e-mail visibility settings doesn't change a thing.
Do you guy know any solution to this ? how to create an issue with email? cause i tried "reporter":{"name":"name.lastname@ID.com"} and it came empty. ?
Thanks in advance for any idea !
Solved! Go to Solution.
Hey @Petter Gonçalves ,
I'm running a Jira Server instance and for search for a user I'm using
GET /rest/api/3/user/search?query=<e-mail>
And I'm still getting the username not supported error. I'm not even passing the username here.
Hi @Petter Gonçalves ,
I'm running a Jira Server instance and i like to search a user.
Currently i'm calling the :
GET /rest/api/2/user/search?query=<e-mail>
It returns the 'Username' not supported error. I'm not even passing the username field. Is query supported for Jira Server users?
Hello @Anushaath
As far as I checked, the deprecation of usernames is only applicable to Cloud, so you should be able to still get the relevant users by using their usernames:
get http://www.example.com/jira/rest/api/2/user?username=fred
Let me know if that endpoint still works for you.
It works without any more issues: https://vistaprint.atlassian.net/rest/api/3/user/search?query=example@domain.com
Yes thank you @Petter Gonçalves .
The Jira server implementation indeed accepts the username parameter.