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!!
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.
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.
Hi there! Shannon from Statuspage here. 👋 With Cyber Monday quickly approaching, we're looking to hear from Atlassian customers – specifically from teams who touch incident response li...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs