nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira Rest API not able to search for users after first 100 even using startAt 100

ChristopherChilds

This is strange.

We have only noticed this since upgrading to Jira 10.3.11

It is an API we do not user regularly, however, we are not able to search for users beyond the first 100 available users.

for example

If I user the following:
/rest/api/latest/user/search?username=.&startAt=0&maxResults=100

I will get 100 results. However, if I were to increase the startAt to 99 for example I get a single result where the user is equal to the last user in the first call (the 100th user)

I have tested this against issue search and I do not get this problem. It seem that the response is different for Issues as they are paginated.

Accepted answers

unknown

Hello @ChristopherChilds

What you have encountered is a well known issue with that REST API endpoint that happened with the release of Jira DC v10

Refer to JRASERVER-78660

All comments

David Nickell

This has turned out to be more interesting than I thought. I want to go a little further, but here has what I've realized so far.

There are "User" endpoints and "UserSearch" endpoints. Your variation seems to be the Search (single "user" in the path) which would seem to be Jira oriented based on the endpoints

I have tested the Users variation and it works exactly as you expect (users plural in the path). It seems to be more system/instance .. not Jira App specific

Both User and UserSearch say they return an array of users and both support the statrAt and maxResults parameters. I may update your question once I confirm when/why/where on User "get" is appropriate versus trhe other.

I am going to work little more-- and I am surprised I never noticed. The screenshot is from an internal tool... if you go to the atlassian documentation, both endpoints are there right next to each other

thanks

unknown

Hello @David Nickell

The OP's question is about Jira DATA CENTER's V2 REST API endpoint... but you are showing and talking about endpoints from Jira CLOUD's V3 REST API, which is a totally different thing in a totally different product.

unknown

Hello @ChristopherChilds

What you have encountered is a well known issue with that REST API endpoint that happened with the release of Jira DC v10

Refer to JRASERVER-78660

ChristopherChilds

Great thanks for the link. I did search but I was not searching correctly.

David Nickell

I totally appreciate the information. Thanks

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

rest-api

jira-data-center