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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

"504 Gateway Time-out error" while doing bulk changes

Hi Team,

While trying to bulk move issues to another issue type within the same project we are getting "504 Gateway Time-out error".Our maximum bulk change limit is 1000 issues, when we try with issues less than 600 it is working fine and if we go beyond 600 then we are getting this error.After this had happened we have checked with our connection timeout and it was 20 seconds, we increased it to 60 seconds and tried but no use.Any solution on this?


1 answer

0 votes
Charlie Misonne
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 18, 2023

Hi Harsha, welcome to the Atlassian community!

Since you increased the timeout to 60s: do you get the timeout after 60s too or is it shorter?

60s might still not be enough to process 1000 issues.

This bug could also be related to your issue:
What version of Jira are you on?

Hi Charlie, even after increasing it to 60s also we are getting same error but it is not holding till 60s within 20-30s we are getting this error if we try more than 600 issues

we are currently in 8.22.3 version of jira, hosted in AWS

Suggest an answer

Log in or Sign up to answer