The query parameter 'username' is not supported in GDPR strict mode

[Surya Kandyanam]

we have been getting this error, while running the deployment to prod. it was working fine but now its not. please let us know what to change since it not accepting email

def requestor = jiraUserSearch(queryStr: "${requestorEmail}", site: "${jiraSite}").data[0]

JIRA: Site - caleres - Searching JIRA Active Users: skand@--- startAt: 0 maxResults: 1000

Error Code: 400

Error Message: {"errorMessages":["The query parameter 'username' is not supported in GDPR strict mode."],"errors":{}}

{"errorMessages":["The query parameter 'username' is not supported in GDPR strict mode."],"errors":{}}

[Surya Kandyanam]

Hi Petter,

we are using a method that  calls user email but now its not working, that method is 

def requestor = jiraUserSearch(queryStr: "${requestorEmail}", site: "${jiraSite}").data[0]

this queryStr gave us this error 

The query parameter 'username' is not supported in GDPR strict mode."],"errors":{}}

how can i get a requestor name using this or other method. If i have to use which method should i use.

Thanks

Surya Kandyanm 

[Amos Shapira]

The documentation in https://developer.atlassian.com/cloud/jira/platform/rest/v3/#api-rest-api-3-user-picker-get still mentions username, is this an error in the documentation?

[Petter Gonçalves]

Hello Everybody,

Thank you for your details and provided information so far.

As you can see in this deprecation notice, Jira REST API has started to use the AccountId parameter instead of 'Username' and 'userKey', so it should be properly working if you have the correct permissions.

If you are not being able to return any information with that parameter, please ask for help is in the Atlassian Developer Community:

https://community.developer.atlassian.com/ 

The mentioned portal was specifically created for development questions, where you will find articles and suggestions from other third-party partners and Atlassian developers. Feel free to open a new topic about your question there if my answer was not helpful.

Let us know if you have any other questions.

[Surya Kandyanam]

thanks petter for giving the developer community. i have changed it to  accountId from username or userkey. But this the method we are calling jirausersearch which is still giving an error for username where it usually calls email address. this is the line thats throwing an error

def requestor = jiraUserSearch(queryStr: "${requestorEmail}", site: "${jiraSite}").data[0]

the code is 

def call(Map config) {
def requestorEmail = config.requestorEmail
def parentJiraIssueKey = config.jiraIssueKey
def projectGroupId = config.projectGroupId
def projectArtifactId = config.projectArtifactId
def projectVersion = config.projectVersion
def rollbackVersion = config.rollbackVersion
def deploymentDescription = config.deploymentDescription
def testingNotes = config.testingNotes
def deploymentType = config.deploymentType

def jiraSite = 'caleres'
def deploymentProjectKey = 'RID'

echo "${parentJiraIssueKey}"

def jiraIssue = jiraGetIssue(idOrKey: parentJiraIssueKey, site: "${jiraSite}")
echo "Found issue: ${jiraIssue.data.key} - ${jiraIssue.data.summary}"
def requestor = jiraUserSearch(queryStr: "${requestorEmail}", site: "${jiraSite}").data[0]

how can i place accountId instead of accountId in this code at requestorEmail in previous line 

echo "Requestor: ${requestor}"

Thanks 

Surya K

[ERIK GAUDIN]

accountId wasn't working yesterday.. only displayed this as response 
[]
This is what i was using yesterday :
https://mydomainname.atlassian.net/rest/api/2/user/permission/search?accountId=theemailiwanttotest@mydomainname.ca&permissions=ASSIGNABLE_USER&assign&issueKey&projectKey=MyProjectKeyHere&startAt&maxResults

now i got a full page that include lot of other user email adress in the response ! It's not only the user query i found now... All user un our organisation starting by the letter "a"

So instead of only got the userpermission i need on this user, and got his ID, so i can automate a TaskCreation in JIRA and assign him as "reporter"... now i got 30 user in the search result.

Don't know why this now, as Atlassian want to "secure" user information.. now i got all of them that start with the letter "a" ... instead of only this user.

I only need the user information... not all of them. Any idea where i can look at ?

[ERIK GAUDIN]

Same for me... the function stop working !

I was using the same querry... now if i change "username" with "accountId" .. I dont get any error, only this : 

[]

[Surya Kandyanam]

which method are you for accountId, can you please share with me. 

[Chen Chia Hung]

Hi @Surya Kandyanam and @ERIK GAUDIN ,

I think the API you mean should be the following, but It works on my side.

https://carousell.atlassian.net//rest/api/2/user/search?accountId=<%accountId%>

But I'm also facing the issue with you, I got the same error message below with you. >_<, Hope we can get a solution as soon as possible.

https://carousell.atlassian.net//rest/api/2/user/search?username=

{"errorMessages": ["The query parameter 'username' is not supported in GDPR strict  mode."],"errors": {}}

[Chen Chia Hung]

Oh ~ sorry, I saw the message below. 

[ERIK GAUDIN]

The way i use this API Call... I built a Google Form... to help user to create task in Jira... without missing any requested information..

This Form are consolidated in a Google Sheet... and a Google Script run when the GForm is trigged...

As i gather the email adress in the GSheet.. i use that to find the proper JIRA userID, and then use it to create the task and add the user as "reporter"... So the user will be aware when someone start working on the Ticket.

I could temporary force a generic user to filled the form, using the proper ID manually... but the user wont benefith of been inform when an action is perform on the ticket.

I also sent an e-mail to the user, with the direct URL of the Ticket... so he only click the URL to access the ticket directly ! Very usefull for those user who don't know how to operate JIRA

[Petter Gonçalves]

Hello @Surya Kandyanam

Thank you for reaching out.

Can you please specify to us what is the action that is triggering the error you are facing? Can you please provide us with a step-by-step process to reproduce the error you are seeing?

Independent of what you are trying to do, I believe the error you are facing must be related to the changes that were implemented in jun/2018 at Atlassian Cloud applications to ensure we are compliant with GDPR policies:

Say goodbye to usernames in Atlassian Cloud

Explaining better, the username field was completely removed from Atlassian Account profiles, so the email address is the unique identifier of Atlassian accounts now.

Please, check if the documentation provided and provide us with the information requested if you still have any questions.

[Rutger Deterd Oude Weme]

cannot be triggered by jun/2018 but something in last week. Today I also get the

"The query parameter 'username' is not supported in GDPR strict mode."

error on a call that was working fine monday last week.

the call is:

https://logexgroup.atlassian.net/rest/api/2/user/search?username=user@company.nl

[Deleted user]

Hi @Petter Gonçalves 

The documentation for both v2 and v3 of the REST API still states we can use username to search.

If `username` is gone, what do we use to search for users now?

Searching by displayName email does not work.

[Deleted user]

Answered my own question. The answer is `query`.