-
Bug
-
Resolution: Fixed
-
High
-
7.2.12, 7.3.8, 7.4.5, 7.5.3, 7.6.3, 7.7.1, 8.5.0, 8.5.1, 8.13.0, 8.20.15, 8.22.2, 9.4.11, 9.12.13
-
7.02
-
79
-
Severity 3 - Minor
-
19
-
-
Atlassian Update – 14 August 2025
Dear Customers,
We're happy to announce that this issue is fixed in the upcoming 11.0.1 and 11.1.0 releases.
Previously, when completing a sprint, users could encounter a generic timeout error message if the process took longer than 60 seconds. Although the sprint data was updated, issues are moved to the new sprint one by one, which could time out for very large numbers of issues or due to instance-specific problems such as a custom field taking a long time to re-index.
We've enhanced the timeout message to provide clearer information about the process status. This improvement is similar to what we implemented for Kanban boards under
JSWSERVER-11775.
While we have a public issue regarding the performance improvement of this operation, you can help increase its priority by voting for JSWSERVER-15345. Please be aware that the root of the performance issue may be specific to your instance, such as particular custom field configurations.
Thank you for your continued patience and support. We are committed to providing you with the best possible experience and welcome any feedback you might have.
Best regards,
Daniel Rauf
Software EngineerAtlassian Update – 14 August 2025 Dear Customers, We're happy to announce that this issue is fixed in the upcoming 11.0.1 and 11.1.0 releases. Previously, when completing a sprint, users could encounter a generic timeout error message if the process took longer than 60 seconds. Although the sprint data was updated, issues are moved to the new sprint one by one, which could time out for very large numbers of issues or due to instance-specific problems such as a custom field taking a long time to re-index. We've enhanced the timeout message to provide clearer information about the process status. This improvement is similar to what we implemented for Kanban boards under JSWSERVER-11775 . While we have a public issue regarding the performance improvement of this operation, you can help increase its priority by voting for JSWSERVER-15345 . Please be aware that the root of the performance issue may be specific to your instance, such as particular custom field configurations. Thank you for your continued patience and support. We are committed to providing you with the best possible experience and welcome any feedback you might have. Best regards, Daniel Rauf Software Engineer
Summary
If completing a sprint takes longer than 60 seconds one will experience a timeout message similar to the following:
Environment
- Bulk editing large amount of issues (200+) takes longer than 60 seconds
Steps to Reproduce
- To reproduce artificially, lower the AJAX timeout to something like 10 seconds and do a sprint release on 3,000 issues
- Have a large number of issues in a sprint (200+) with a To Do or In Progress status category
- Use remote fields, other customizations, or poor performance that results in bulk editing these issues to take longer than 60 seconds
- Attempt to complete sprint using the "Move open issues to: <another sprint>" option, receive error message
Expected Results
A more descriptive error message is displayed like the one we implemented for Kanban boards, https://jira.atlassian.com/browse/JSWSERVER-11775
Actual Results
A generic timeout error is displayed
Notes
Even though a timeout error is displayed the process does continue and issues within the sprint are completed successfully
- is related to
-
-
- Closed
-
- relates to
-
-
- Closed
-
-
-
- Gathering Impact
-
-
FLASH-3711 Loading...
-
- is duplicated by
-
- mentioned in
-
-
-
-
-
-
-