Cloud REST API "Find users by query" endpoint issue

Hey,
I have an issue with the provided endpoint. https://developer.atlassian.com/cloud/jira/platform/rest/#api-api-2-user-search-query-get

When I perform a query of getting all the users who are an assignee of a project then the inactive users are not returned. Is there an option which I can use to get inactive users as well?

Thanks in advance,
Oliver

This is a new experimental API and filtering for active and inactive users is not supported yet.

Regards,
Dave Meyer
Jira Product Management

1 Like

Okay, thanks.

Can this feature be requested? Or at least the reference guide should note this as this means that some of the issues are not returned.

Actually I have come to a situation, that it is impossible to get a list of inactive users.

There is the following endpoint as well, which I would expect would help me.
https://developer.atlassian.com/cloud/jira/platform/rest/#api-api-2-user-search-get

But the first example given there, is wrong - the query cannot be made without one (either username or property given as request parameter).

Can you explain, is there a way to get a list of inactive users?

Hi @oliversoop,

I created https://ecosystem.atlassian.net/browse/ACJIRA-1440 for you to track this improvement. Jira Cloud currently doesn’t support an API to return all users in a site without a search parameter, and we have no plans to provide one.

Dave

1 Like

Hi @oliversoop,

By default, all users are in the ‘jira-users’ group, so you can use this endpoint: https://developer.atlassian.com/cloud/jira/platform/rest/#api-api-2-group-member-get
You may need to query a different group if the default was changed.

I don’t see a way to get a list of inactive users aside from making two requests, one with ‘includeInactiveUsers=true’ and one with ‘includeInactiveUsers=false’ then comparing the results

–Simon Kinsler

Hi @oliversoop,
I’m the developer maintaining the endpoint you mentioned in your original question.
From next week, it will support returning inactive users as well.
You can track progress in the issue created by @dmeyer here. The docs will be updated when the change hits production.
Let me know if you have any further questions.
Best regards,
Simone Russo