Need this bug fixed so that the report will be accurate.

Three reasons we need this:

1. On large projects with multiple stakeholders, executive reporting is required. Providing visibility into release burndown/burnup is a critical piece of this reporting. This reporting is often done with Confluence pages with additional project context (financials, risks, milestones, quality metrics, etc) or dashboards. Not being able to embed a release burndown/burnup chart into either of these is not only incredibly frustrating, it makes me question Atlassian's basic understanding of how their customers use Jira.

2. Until now, on some projects, it has been possible to use the Agile Rapid boards in conjunction with Agile Classic gadget (with a filter) to track release burndowns by story points in Confluence and dashboards. With classic features scheduled to be removed in the next release, this option goes away.

3. Our organization uses wallboards to radiate information to project teams. We like to include release burndowns/burnups on wallboards so that at all times the team knows how we're progressing on our product roadmap

Added a vote as well. Would be extremely helpful.

Adding my vote to this issue. As a long time user of Agile Classic (GreenHopper) I have had a tough time since upgrading to the newer Agile plugin creating meaningful dashboards for stakeholders of long running Scrum projects. The main reasons are lack Agile gadgets and surprising feature limitations like GHS-7664.

I'm surprised at the lack of movement around suggestions such as this. I can only guess at the complexity of adding these specific features. But I wonder why a greater priority would not be assigned to creating meaningful dashboards. At our organization at least, this used to be big part of demonstrating the value of Jira to stakeholders that control our budget and support of such tools.

Apologies intersol_OLD, I've updated the link.

The linked page from documentation was removed...?

I represent an organisation of 300 within a company of 7000.
We'd like this for our many users a lot please.
We use JIRA Agile and Dashboards everywhere.

I agree that this would fit my need for the scope change.

Hi there,

Regarding "improving accuracy" of the version report, have you seen our latest iteration on release reporting called the "Release Burndown"? You can read more about it in our documentation.

Regards,
JIRA Agile Team

Let me add my voice to this request. Providing a dashboard of versions would make reporting progress for a team with many stakeholders much easier.