user/assignable/multiProjectSearch sometimes capped to 100 users

[Ian Fillion-de Kiewit]

Something weird is happening when I try to get a list of assignable users to a project.

Path:

/rest/api/2/user/assignable/multiProjectSearch

Params:

{startAt: 0, maxResults: 1000, projectKeys: "UC"}

Issue:
The amount of users is somehow capped to 100. Paginating does not help. Even if I set maxResults to 90; the first response contains 90 results and the second response contains 10 results.

I know that there are more than 100 users that should be returned from this endpoint. If I use the "query" parameter and loop through every letter, I get all 143 results as expected.

I don't mind using the "loop through every letter" method for worst-case scenarios (usually when the amount of users is over 1000), but this limit of 100 seems completely arbitrary. I can use the same query with "maxResults: 1000" on another user / project to get over 200 users in a single API call.

-----------------------------------

So the main question here is: Why is this endpoint capped to 100 users for this particular project or user? Is there a way to change this to at least 1000?

Thank you

[Srikanth Inuganty]

I am facing the same challenge as above.  Can someone please suggest how to get around this.  This api results are capped to 100 rows. Parms used are :

/rest/api/2/user/assignable/multiProjectSearch?projectKeys=RPSO&startAt=0&maxResults=250