Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-8829

Burndown Gadget to show multiple sprints or to Version burndown

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Answered
    • None
    • Gadget
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Previously in Classic Statistic Burndown Gadget, it can be configured to show results for a Project or a Product. If the current Sprint Burndown gadget can be configured to have multiple sprints, it could show the progress of almost a complete product (which is the goal). Perhaps when it is configurable to multiple sprints, it also can be limited to a version.

          Form Name

            [JSWSERVER-8829] Burndown Gadget to show multiple sprints or to Version burndown

            Olivia Cohen added a comment -

            Are there any news since 2014? Thanks

            Olivia Cohen added a comment - Are there any news since 2014? Thanks

            Martin (Inactive) added a comment -

            JIRA Agile 6.5 will see the Release Burndown chart, which is currently available in JIRA Agile Labs.
            This might be of interest : https://confluence.atlassian.com/display/AGILE/Labs+-+Viewing+the+Release+Burndown

            Regards,
            JIRA Agile team

            Martin (Inactive) added a comment - JIRA Agile 6.5 will see the Release Burndown chart, which is currently available in JIRA Agile Labs. This might be of interest : https://confluence.atlassian.com/display/AGILE/Labs+-+Viewing+the+Release+Burndown Regards, JIRA Agile team

            Maree Milne added a comment -

            Hi guys - this feature is important to us as well. Is it being tracked somewhere else? I don't think it's actually resolved.

            I appreciate that you didn't see it being worked on soon in August 2013, but we're now in July 2014 so is this going to be revisited?

            Maree Milne added a comment - Hi guys - this feature is important to us as well. Is it being tracked somewhere else? I don't think it's actually resolved. I appreciate that you didn't see it being worked on soon in August 2013, but we're now in July 2014 so is this going to be revisited?

            Intel CHD Jira Admin added a comment -

            Why this feature is useful:

            If the estimation metric is time, the version report only gives information about original estimated time, not remaining estimated time. What we'd like is a version burndown, comparable to the sprint burndown.

            If the sprint burndown was implemented in a generic way, it must be easy to extend to a version burndown. It's just a burndown with a different way of determining the list of issues...

            -David

            Intel CHD Jira Admin added a comment - Why this feature is useful: If the estimation metric is time, the version report only gives information about original estimated time, not remaining estimated time. What we'd like is a version burndown, comparable to the sprint burndown. If the sprint burndown was implemented in a generic way, it must be easy to extend to a version burndown. It's just a burndown with a different way of determining the list of issues... -David

            Intel CHD Jira Admin added a comment -

            Is "Answered" a different way of saying "won't fix"?
            -David

            Intel CHD Jira Admin added a comment - Is "Answered" a different way of saying "won't fix"? -David

            Martin (Inactive) added a comment -

            Thanks for reporting this issue. We see this as a valid feature request, however realistically we will not be working on it in the next 12 months.

            Thanks for your patience and we hope you appreciate our open approach to feature requests.

            Regards,
            GreenHopper Team

            Martin (Inactive) added a comment - Thanks for reporting this issue. We see this as a valid feature request, however realistically we will not be working on it in the next 12 months. Thanks for your patience and we hope you appreciate our open approach to feature requests. Regards, GreenHopper Team

              tkotecki Tom Kotecki (Inactive)
              znoorsazali Zul NS [Atlassian]
              Votes:
              4 Vote for this issue
              Watchers:
              15 Start watching this issue

                Created:
                Updated:
                Resolved: