This is related to the linked question on Atlassian Answers.

The version report as a dashboard and wallboard gadget will be available soon in JIRA Agile 6.7.0

Kind regards,
Martin
JIRA Agile

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

Martin - I appreciate that ... however this issue is nearly 2 years old is currently unassigned and has had no activity upon it from Atlassian other than for it to be triaged.

Forgive me if I don't hold my breath in waiting for this.

david.grierson1, we understand that gadgets are an important part of reporting and plan to add support for each of the reports.
The Version Report gadget is the highest priority of the remaining reports that do not currently have gadgets and we plan to deliver it in an upcoming version of JIRA Agile.

Kind regards,
Martin
JIRA Agile

It looks like the gadgets provided by JIRA agile haven't moved since version 6.0 was released.

There have been a heap of new reports provided by JIRA Agile - which is a good thing. However the generation of any new report should have a corresponding required activity to provide this as a pluggable report via a gadget for that report.

JIRA reports are information related to how a project is progressing - these are the kind of information which management teams want to see provided in a summarised report. For example in a Confluence page combined with all sorts of other pieces of information (financials, team allocation, capacity management, team holidays, key events, etc. etc.)

By failing to provide this information in a pluggable format you're failing to stand out amongst the crowd of vendors who are all trying to tie you into a single environment/ecosystem.

Don't be like the others - you used to get it right ... why not any more?

+1 to Peter's comment.

Our management team loves the Version Report, but isn't reasonable for them to go into each team's scrum board to view them. They really want a dashboard or any way to view many different team's Version Reports at the same time.

+1 to Peter's comment

+1 to Peter's comment.

In my opinion, all reports that can be generated using the Report mode should be available as gadgets so I can display them on a JIRA dashboard or on a Confluence page.