Before the GDPR API changes, we were able to query all users (up to 1,000) by making this call `/rest/api/2/user/search?username=_&maxResults=1000`. This would return a list of 1,000 users in JIRA. Since the GDPR changes, we have noticed inconsistencies with the API. We are now limited to 100 users (this is not a documented default) regardless of the maxResults specified.
Also, the query parameter `username=_` with the wildcard of `_` does not seem to work anymore. Adding no query parameter value returns users but only up to 100.
We have tried setting `startAt` to `100` and `maxResults` to a higher value, but we are not able to get any users past the first 100.
We are able to get users by id, but since we have over 1,000 this is not a viable solution.
We need a way to get al users.
Is there a way to get around this?
Is there a way to paginate after the first 100 users?
Is there any updated documentation?
Any guidance or help would be appreciated, thank you.
Hi Alejandro,
With the changes to user privacy in accordance with GDPR there were some major overhauls to the available data in the user related endpoints.
I believe the comparable endpoint you are looking for is "/rest/api/3/user/search?query=%" to fetch all users, as detailed in the comments of the related endpoint update ticket that is located in the table of related tickets about half way down the the article in our developer space "Major changes to Jira Cloud REST APIs are coming to improve user privacy" for the full details on the applied changes for GDPR.
The direct ticket noted is linked below but I just wanted to make sure you had the full list as a referance point incase you had any follow up questions:
Regards,
Earl
Hi @Earl McCutcheon rest/api/3/user/search?query=% API doesn't work for us anymore. Do you have an idea why and is there any other API which would work to get all Jira users?
Thanks,
Lukas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Lukas Krajnak ,
I just double checked to verify, and the endpoint is still functioning and should be good. What are you seeing when you hit the endpoint? Are you getting an explicit error?
Regards,
Earl
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.