The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Request to get issues from jira api results in timeout.

muhammad_mansoor
October 1, 2018

When I try to get issues for more than month, request results in timeout. Is there any best alternative to it that will not affect the performance?

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

3 votes
Answer accepted
Daniel Eads
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 1, 2018

Hi Muhammad,

There's several things that could be at play here.

  • Do you have a reverse proxy configured in front of Jira? Apache, nginx, etc may have a default timeout value that you need to increase for your API call to complete successfully.
  • Is the server you're running Jira on underpowered (not enough RAM, fast enough disk, enough processors, etc) or do you have Jira configured to use enough heap? Check out the sizing guide (written for Jira 6, inflate the numbers a little bit) to see if you may be under-resourced.
  • Can you reduce the number of issues returned in the API call, or reduce the number of fields you're trying to retrieve?
  • Can you paginate the results (retrieve smaller sets of issues at a time)? See this previous Community post for an example of pagination.

Cheers,
Daniel

muhammad_mansoor
October 1, 2018

Thanks @Daniel Eads for your response. Reducing the number of fields solved my problem.

TAGS
AUG Leaders

Atlassian Community Events