user getting "error timed out" message when loading agile board

I have users in India (the server is in the US) that are getting a "request timed out" error (see image at end) when trying to load an agile board to do planning.  There are ~300 items in the backlog and ~50 in the sprints, so we're not talking about a huge amount of data.   A US client can load the board successfully.


Does anyone have any ideas about what I can try next?



The JIRA server logs show nothing.  I did up the agile and plugin logging to DEBUG, but still nothing useful.  Google is also a bit silent on the issue as well.

Things we're trying:

I'm open to ideas.


1 answer

I think that the time between the request to the serveur and the reply is too long.

Maybe, your server is too slow, or too busy. It may require more memory or more CPU.

The internet traffic may cause this too long response.


I agree that latency is most likely the issue here. I'm able to run the agile board successfully on a LAN close to the server, so it's probably not a memory or CPU issue (unless there's a huge traffic/user spike that I'm not aware of during GMT +5:30.) I was hoping that someone was aware of some server or plugin tweaks/settings that could help.


I am having same issue in my current instance of JIRA and all users are in US and we noticed this issue with one board and that board is trying to load close to 4K issues. Has anyone figured out any solution?


Subodh, I'm seeing the exact issue you are describing, but with a smaller number of issues.  I was wondering if you found any solution to your issue.

Myra, Our instance of JIRA and JIRA Agile plugin has a known issue about error time outs.

Please see the below KB article that was given to me by Atlassian. Atlassian asking us to upgrade JIRA (This was the solutions I was given by Atlassian support).

Hi Subodh, thank you for getting back to me.  I found the issue in ours.  It has something to do with one of the issues that was being pulled into the board.  It must be some kind of overflow or bad index, or something.  If I try to bring up the issue on its own, JIRA is not able to.  This link below pointed me to consider a potential overflow... although it's not JIRA.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Wednesday in Jira

Make your Atlassian Cloud products more secure: our NEW admin security guide

Hey admins! I’m Dave, Principal Product Manager here at Atlassian working on our cloud platform and security products. Cloud security is a moving target. As you adopt more products, employees consta...

155 views 0 6
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you