-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
Severity 3 - Minor
-
Issue Summary
When attempting to perform a bulk edit from the filter page in Jira Cloud, users encounter a 504 Gateway Timeout error on the first bulk edit screen if the filter returns around 300 issues. This occurs well below the documented 1,000-issue limit for bulk operations. The issue is site-specific and not user-specific. The new BulkOps Toolbar is not available on the filter page, so the legacy bulk edit flow is required for this use case.
Steps to Reproduce
- Log in to Jira Cloud as a user with bulk edit permissions.
- Navigate to a filter that returns approximately 300 or more issues.
- Click the “...” (more) dropdown and select “Bulk change work items.”
- Observe the behavior on the first bulk edit screen.
Expected Results
The first bulk edit screen should load successfully for up to 1,000 issues, as per Jira Cloud’s documented limits, allowing the user to proceed with the bulk operation.
Actual Results
A 504 Gateway Timeout error is displayed on the first bulk edit screen when the filter returns around 300 issues. If the first screen loads, subsequent steps work as expected.
The below exception is thrown in the HAR file and browser console (no relevant entries in Splunk logs):
{{}}
Request URL: https://amdpoc-sandbox-march18-swdev-mig.atlassian.net/secure/views/bulkedit/BulkEdit1!default.jspa?reset=true&new=true&tempMax=1000 Status Code: 504 Gateway Timeout atl-traceid: 0e9978c2a5f34f139d304799bf763f97 <html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx</center> </body> </html>
{{}}
Workaround
- Reduce the number of issues in the filter to below 300 before initiating the bulk edit from the filter page.
- Alternatively, use the new BulkOps Toolbar in the backlog or issue list views (if available), though this does not cover all filter-based use cases.