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!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Bamboo API: quicksearch only returns 12 results

When curling


I'm getting back a json object with "size: 12" when there should be quite a few more than 12 results. Specifying max-results doesn't change anything, it will restrict the results to a number less than 12 but doesn't increase it to anything more than 12. 


Is there some other parameter I can pass that will force it to return more than 12, or is quicksearch just limited to 12? Does anyone know? Thanks!!

1 answer

1 vote
robhit Atlassian Team Nov 15, 2017

Hi Emmett,


How about trying this:



1. The above will give you max result =1



2. Will give you all


Let me know if it doesn't works

Thank you for your response!!

Option 2 still only returns 12, even with a searchTerm that should return hundreds of matches. It's like the max-results parameter is applied after the result set is returned from the search. The search returns 12, then it applies max-results to that 12. It will limit it if max-results is less than 12 but can't return more than 12 because the result set was already limited to 12 before max-results is even applied.

robhit Atlassian Team Nov 17, 2017

Hi Emmett,


Yes, you are right. It is limited to 12 only.

I believe it because of the fact that the result is paginated probably because if you do not have pagination you will face performance issues while getting all the data.

I also tried adding "&start-index=2" to see if I can loo into the next one:


But, it seems it is also not giving the result.

Let me know if you can build a loop around this parameter.

I have the same problem. Any solutions to this?

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events