Currently, only the "search" endpoint supports parameters for filtering the tickets.

Unfortunately, as documented HERE: It can take up to a few minutes for new tickets, users, and other resources to be indexed for search.

We need near-real-time data as part of our use case, so we resorted to using the "users/{user_id}/tickets/requested" endpoint instead.

However, this endpoint doesn't support any filtering parameters. It returns ALL tickets for a given requester. This also means that it takes a long time to return the results (including pagination) when the total number of tickets is nearing 1000.

In our use case, we only need the unsolved tickets for a given user, and we need the most up-to-date results. Our application often times out when fetching results for a user with too many tickets. Unfortunately, we have no option to change the timeout setting.

We request that, as a simple solution, to please add a "status" parameter for the "users/{user_id}/tickets/requested" endpoint, so that the data output would be reduced and results would be returned faster.

Thanks