-
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
-
-
- Closed
-
- addresses
-
CHER-2079 Failed to load
- blocks
-
ACE-5993 You do not have permission to view this issue
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- relates to
-
[JRACLOUD-90404] Performance issues in agile reports with a large history or number of issues with potential timeout failures
We understand the difficulties you have experienced with the velocity report in your Jira projects, particularly regarding loading failures caused by timing out.
We have developed a solution to address this issue and improve performance significantly, while also preventing future timeouts. This solution is currently available for customers to opt-in but has not been rolled out to all users yet.
We are reaching out to inquire whether you would like us to activate this feature on your instance as we continue working towards a wider release of the solution. If you wish for us to enable this for you, please submit a customer support ticket so that we can proceed accordingly.
Please note that this fix exclusively pertains to the velocity report and does not affect other reports.
Your feedback on the effectiveness of the solution would be highly valued.
Our team has been working to further improve the velocity report in Jira. Our main focus has been enhancing the report’s reliability, particularly addressing the timeout issues experienced by some customers. As part of these changes, you may notice the “Prioritize page load time” toggle has been removed. This is part of our new approach to processing the report data, improving reliability, and preventing timeouts. While this may not directly increase loading speed, it’s designed to provide a more stable experience overall.
If you experience any performance issues or have any concerns, please submit a customer support ticket. Your feedback is important as we continue to improve these reports.
Over the past several months we have delivered a variety of upgrades and fixes that have made major improvements the performance of the velocity report as well as the sprint, burndown, burnup, cumulative flow report and control chart reports.
We feel confident that the timeout issues users were experiencing with the velocity report should now be resolved and performance overall has been significantly improved. As such, we are closing off this bug now.
If you continue to experience any performance issues related to the velocity report please raise these here. Performance issues with other reports can be raised separately.
All comments
Our team has been working to further improve the velocity report in Jira. Our main focus has been enhancing the report’s reliability, particularly addressing the timeout issues experienced by some customers. As part of these changes, you may notice the “Prioritize page load time” toggle has been removed. This is part of our new approach to processing the report data, improving reliability, and preventing timeouts. While this may not directly increase loading speed, it’s designed to provide a more stable experience overall.
If you experience any performance issues or have any concerns, please submit a customer support ticket. Your feedback is important as we continue to improve these reports.
We understand the difficulties you have experienced with the velocity report in your Jira projects, particularly regarding loading failures caused by timing out.
We have developed a solution to address this issue and improve performance significantly, while also preventing future timeouts. This solution is currently available for customers to opt-in but has not been rolled out to all users yet.
We are reaching out to inquire whether you would like us to activate this feature on your instance as we continue working towards a wider release of the solution. If you wish for us to enable this for you, please submit a customer support ticket so that we can proceed accordingly.
Please note that this fix exclusively pertains to the velocity report and does not affect other reports.
Your feedback on the effectiveness of the solution would be highly valued.
Still waiting for this to be fixed! Projects with long life span are affected in performance and report-generation wise still
According to Atlassian's bug fix policy, "Atlassian begins work on Highest priority bugs as soon as reasonably possible.". I guess 33 months do not fit into "as soon as reasonably possible" theory.
Any updates on an ETA?
I see this marked as High Priority, however it has been open for a long time.
Is it possible for an unofficial update on this one?
Our use case is that we are using advanced roadmaps and the Team field. This is creating complex queries and now is stopping our teams from using the default reporting.
This is a significant draw back as we just shifted to using Advanced Roadmap (Jira premium) to manage portfolios.
Thanks in advance for any updates.
Please when i select from people menu tab and search for a team member , and click on view all for his/ her worl log , i recive this bug "Something went wrong"
As a Jira Admin, I am unable to identify the filter used by each board via a single API call. I must use 3 sets of API calls to identify what filters may require modifications. See my comment in JSWCLOUD-20535 Add the ability to define board configuration through the REST API
Pinned by
Simon Taylor
Over the past several months we have delivered a variety of upgrades and fixes that have made major improvements the performance of the velocity report as well as the sprint, burndown, burnup, cumulative flow report and control chart reports.
We feel confident that the timeout issues users were experiencing with the velocity report should now be resolved and performance overall has been significantly improved. As such, we are closing off this bug now.
If you continue to experience any performance issues related to the velocity report please raise these here. Performance issues with other reports can be raised separately.