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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,559,889
Community Members
 
Community Events
185
Community Groups

Jira Cloud Rest API - Search Method - maxResult issue

Edited

What

From today when we call to search method (issues) in Cloud Rest API and we set maxResults=1000 (or other value greater than 100), system is always returning 100 issues.

Endpoint example

https://xxx.atlassian.net/rest/api/2/search?maxResults=1000&jql=project="YYY"+order+by+updated+asc

Response example

{
"expand": "schema,names",
"startAt": 0,
"maxResults": 100,
"total": 428,
"issues": [{...}]

}

Question

Is this a Jira REST API bug? or is a no documented change?

 

Thanks in advance!

1 comment

Jira Support answer: 

this change of behaviour is actually intended since calling searches with maxResults set to 1000 in some cases it was causing OOM errors and it was bringing down JIRA.

 

I don't understand how they can do something like that without any advise :(

Comment

Log in or Sign up to comment