Jira Software shows server contact error and doesn't show the content of dropdown fields

Question

Hi, I have two concerns:

1-  With a frecuence of 2 months more or less, the JIRA Software (server version) starts showing the message "Jira server was not found, but has returned an error response" when trying to select users throw the different dropdown fields (informer, responsible, etc.). The workaround we are applying is to restart the JIRA server, sometimes including the JIRA database and it works. But I would like to know what could be causing this behaviour and how to resolve it.

2- I'm experiencing very low performance in the boards. For example, a board that contains 6747 tasks has a delay of 9 seconds aproximately on showing its contest, when searching or when refreshing. Is there any suggestion on how to solve this?

Thanks a lot for your help!

Andy Heinzer · Answer

Responsible is not a system field, so I can't say for sure.  But this same problem can happen to other user fields like reporter or assignee.  If your responsible field is a user field like one of those, then yes, that bug is clearly the one you are seeing here.   I'm confident that upgrading to a newer version of Jira will fix that problem.

Jean Christophe Bénistant · Answer

Hi! I can see bug 63109 is showing the same error as the one I reported, but the cause is  quite different. In my case, the error is shown when making a click in the Responsible field. As the System, for some reason can't connect to the server, it shows the error. After 2 or 3 attempts, the connection is stablished. In some cases, those attempts didn't work, so we had to restart the server.

Maybe the fix also resolves my problem. I hope we can get some budget to update our version.

Thanks!!

Andy Heinzer · Answer

Hi Emilia,

That version of Jira is susceptible to these pair of bugs about user fields: https://jira.atlassian.com/browse/JRASERVER-63109 and https://jira.atlassian.com/browse/JRASERVER-62628

I think they account for the first behavior you described.   I would recommend upgrading Jira to a version such as 7.2.6 or higher in order to fix that problem.