Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,570
Community Members
 
Community Events
176
Community Groups

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

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 ! 

1 answer

1 accepted

4 votes
Answer accepted

Hello @Khalil Ben Amor

Thank you for reaching out.

The error you are facing happens because of the implementation of the new European General Data Protection Regulation (GDPR), where the parameters used to identify users in REST API as "username" and "userKey" were replaced by the Atlassian account ID (accountId).

You can find more information regarding this change in the documentation below:

That being said, you must specify the accountId in the REST API to return the users of your Jira Cloud site:

GET /rest/api/3/user?accountId=xxxx

You can also search for the user's e-mail with the following API:

GET /rest/api/3/user/search?query=<e-mail>

To know the Account ID of multiple users by their usernames, you can use the experimental Endpoint below:

GET /rest/api/3/user/bulk/migration?username=xxxx&username=xxxxx

 Let us know if you have any questions.

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.

Like Anushaath likes this
Like # people like this

Yes thank you @Petter Gonçalves .

The Jira server implementation indeed accepts the username parameter.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events