-
Bug
-
Resolution: Fixed
-
Highest
-
114
-
Severity 3 - Minor
-
70
-
-
Issue Summary
If a board has a broad JQL query and/or long history, causing its reports to go through a large number of issues & history, the reports may experience long load times and fail to load with timeout errors.
Steps to Reproduce
- Create a board with a broad JQL query, for example, one that includes all projects on an instance
- Try loading a sprint report
Expected Results
The report should load data from all the included issues within a reasonable time period. A reasonable time period would ideally be under 4 seconds, but may simply be considered under 10s. Currently large reports may take tens of seconds to load.
Actual Results
The report takes tens of seconds to load or does not load due to timeout exceptions.
Workaround
The only available work-around at the moment is to use less broad JQL queries to use reports that contain less issues and history.
- is duplicated by
-
JRACLOUD-87878 Reports not loading (timeout)
-
- Closed
-
- relates to
-
JRACLOUD-95641 JSW Reports fail to load due to a timeout on sites with a long Work Item history
-
- Gathering Impact
-
-
ACE-5988 Loading...
- addresses
-
CHER-2079 Loading...
- blocks
-
ACE-5993 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...