-
Bug
-
Resolution: Unresolved
-
High (View bug fix roadmap)
-
None
-
7.3.8, 7.4.5, 7.2.12, 7.5.3, 7.6.3, 7.7.1, 8.5.0, 8.5.1, 8.13.0, 8.22.2, 8.20.15, 9.4.11, 9.12.13
-
7.02
-
77
-
Severity 3 - Minor
-
13
-
-
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+ )
- 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, 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
- relates to
-
JSWSERVER-11775 Timeout errors when releasing a large amount of issues from a Kanban board
-
- Closed
-
-
JSWSERVER-15345 Improve performance when moving issues to next Sprint contains many issues
-
- Gathering Impact
-
-
FLASH-3711 You do not have permission to view this issue
-
JSWDC-30 You do not have permission to view this issue
- mentioned in
-
Page Failed to load
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...