Timed out error while trying to bulk edit in Jira Data center

Deleted user March 21, 2018

Hello Team,

white trying to bulk edit issues in Jira ,We are getting timed out error,

I noticed that If we start Bulk edit in one node(Eg-Node1) after some time it will automatically switch to another node(Eg-Node2),

Other operations are smooth ,But we are facing this issue..

Please suggest the right way for the solution .

Server : Jira Data Center,

Version : 7.2.10

 

Thanks & Regards,

Varun Joseph Allu

2 answers

0 votes
Sri R
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 31, 2022

JIRA can't be improved anymore due to its monopoly in the industry and never address any bugs.

0 votes
Mauricio Karas
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
April 18, 2018

Hey, Varun.

Your proxy could be causing the timeout error, the bulk edit operation is taking a while to process and no response comes from the server, so the proxy times out.

If you try to bypass the proxy and access directly one node, does the same error happens? You can check this KB article for the steps on how to bypass the proxy.

Kind regards,
Maurício Karas

Deleted user April 18, 2018

Thanks for the reply @Mauricio Karas

 

The issue is not reproducible to me as one of user reported this,

When I m trying to edit some 500+ issues I am not getting this error,

It's a strange behaviour.

If there is an error with the proxy, then the issue should be for every user and every time,

But the scenario is different.

 

I raised a PS ticket to Atlassian with HAR file and logs nut in vain,

Please suggest how to resolve this issue,

 

Regards,

Varun

Jyoti Bisoi February 26, 2019

Hi, Did you get any solution. We are facing same issue.

varun February 26, 2019

Hello Jyoti,

 

There is no permanent solution for this issue,because it is not from our Jira server side,

It might be issue from IE browser or any of the plugins installed in browser,

Try to do it Private browser as a work around or delete all cache from the browser and try.

It worked for us.. :)

 

Thank you,

Varun

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events