The gadgets released do not equate to the classic agile ones. The classic ones allow you to display a burn down or burn up by version and you have to input the start and end dates for the version in the classic board. With the classic boards no longer being supported, we need to have a gadget that provides the same functionality - ability to display burndown/burnup by issue count, story points, business value by version or a select filter.
The classic boards should not be deprecated without having a gadget that provides the same information as these are critical for all summary and executive level release planning/risk reports.

Hi cesposito,
The gadget was released in version 6.1.6, the release notes are available here: https://confluence.atlassian.com/display/GH/GreenHopper+6.1.6+Release+Notes#GreenHopper6.1.6ReleaseNotes-Newgadget%3ASprintBurndown

The recommended upgrade is to update to the latest version of GreenHopper, there is no patch as such.

What version is this included with? If we're on an older version that has the Rapid Boards, is there a patch that we can add without having to go through an update?

Hi kevin13,
This is achievable in the released product today. Your board must be configured under Estimation to use "Remaining Estimate and Time Spent". When this is done, the burndown chart will reflect these values.

Hi, I assume this has not been Released yet? I am looking for a traditional 'Remaining Hours in Current Sprint' Burndown Chart. Will this work for us? I would really like this Burndown Chart to be visible on the Agile Board and not only on the Dashboard.
Thank you
Kevin

Ediwn - we cannot use that because there is no equivalent yet for the classic agile gadget. The classic agile gadget provides a significant amount of statistics and charts for a product version and you can assign that version in JIRA. We use that gadget for ALL of our executive and board reporting for all of our products and their release risk and targets (we have about a dozen products always in development).

I also cannot turn on the lab feature because it becomes available for everyone and it would cause too many questions amongst the numerous teams we have using greenhopper. I've evaluated it and it doesn't yet meet our requirements due to the lack of supporting gadgets and not worth the time to add yet another item in the process to maintain. I think it is heading in the right direction, but does not yet fulfill the needs of what users are utilizing the classic boards for.

I added a comment on the referenced item because, as it reads, the story doesn't seem to convey the same requirements or request mentioned here.

estol, karie.kelly@phytel.com it looks like what we're specifically talking about is this Story: GHS-7741, which describes the marriage of the Release Planning feature with the Report mode. Pls vote for and watch that issue.

karie.kelly@phytel.com, have you considered using the 'Release Planning' labs feature?
What you describe could be done with that, imho.

Shaun,
When do you expect to have a replacement for the agile gadget that is based on version? This is what is needed for exec reporting as exec don't care about the sprint details - sprint details are for teams...execs care when we are delivering the features to a customer which, in many cases, is a version that consists of multiple sprints and, if there is risk associated with the current targeted schedule. That's the reason we utilize the agile gadget for all exec reporting.