Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Jira Rest Api to fetch assignees giving limited result

I am currently using below rest api for non-cloud jira server to fetch assignees, it is just giving maximum 100 assignees, and pagination is also not working after 100 though many users are present.

<Base url>/rest/api/2/user/assignable/search?project=<project key>&startAt=50&maxResults=100


I need all the users of the jira connection, but limited users are coming.

1 answer

1 vote
Vamsi Kandala
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Feb 25, 2023

Hi @Shivani chittauri

Welcome to Atlassian community!

Unfortunately, by default, the REST API returns 50 results which can be further set to maximum of 100 using 'maxResults=100'.  We will have to use the pagination properties like 'startAt' to retrieve the other results.  So, it is better to try to narrow down your search.

Hope this helps.


Hi Vamsi

I need all the users, but this pagination is not working after 100 i.e., I can't startAt=101 and get results. Everytime it is just giving 100 users only.

<Base url>/rest/api/2/user/assignable/search?project=<project key>&startAt=101&maxResults=100

@Shivani chittauri   That's because that particular endpoint no longer supports the >startAt< parameter. So you go with user #0 to #99 and that's it. This change broke many of our client's daily tools, unfortunately Atlassian doesn't seem to be willing to finally fix their *BS*  :-/

You may want to read for yourself:

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events