-
Bug
-
Resolution: Duplicate
-
High
-
3
-
Minor
-
Problem
Boards exhibit prolonged durations of up to 35s in obtaining sprint report results and sometimes timeout with a 500 error.
Environment
Cloud
The affected endpoints are:
- /rest/greenhopper/1.0/rapid/charts/sprintreport
- /rest/greenhopper/1.0/rapid/charts/scopechangeburndownchart.json
Steps to Reproduce
- Create 100,000 or more issues in your project, and include all of them in the board filter;
- Each issue has +/-10 updates made to it
- Pull a sprint report or a burndown chart
- It doesn't matter how many issues are part of the Sprint.
Expected Results
The report should display within 5-10 seconds at most
Actual Results
The report takes at least 35 seconds before timing out
Workaround
It may be possible to resolve the issue by reducing the number of issues included in the board filter.
- duplicates
-
JRACLOUD-90404 Performance issues in agile reports with a large history or number of issues with potential timeout failures
-
- Closed
-