Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-90263

As a Jira Software user, I want to be able to choose which column in a SCRUM board will "burn" data in the Burndown Chart and Burnup chart report

XMLWordPrintable

    • 0

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      .

          Form Name

            [JRACLOUD-90263] As a Jira Software user, I want to be able to choose which column in a SCRUM board will "burn" data in the Burndown Chart and Burnup chart report

            Matthew Hunter added a comment -
            Atlassian Update - February 18, 2024

            Hi everyone,

            Thank you for bringing this suggestion to our attention.

            As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.

            Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it.

            While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.

            Thank you again for providing valuable feedback to our team!

            Matthew Hunter added a comment - Atlassian Update - February 18, 2024 Hi everyone, Thank you for bringing this suggestion to our attention. As explained in our new feature policy , there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order. Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it. While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket. Thank you again for providing valuable feedback to our team!

            Anton Ahlström added a comment -

            Agree 100% with this. We usually consider issues "done" when dev + testing is done, but we don't deploy until a few days after, when a new sprint is started. This constantly makes issues bleed over, and we never complete a sprint to 100%.

            Anton Ahlström added a comment - Agree 100% with this. We usually consider issues "done" when dev + testing is done, but we don't deploy until a few days after, when a new sprint is started. This constantly makes issues bleed over, and we never complete a sprint to 100%.

            Bruce Kibbey added a comment -

            Commenting here in the hopes that it bumps awareness of this.

            Core issue - BurnUp/ BurnDown reports rely on the LAST COLUMN of the board

            Debate against - Scrum purists will declare that nothing is done until it hits the last column, anything else isn't scrum, right right.

            Debate for - Scrum is rarely pure and especially for smaller teams like mine, we have columns for testing and documentation that we'd like to consider as "Scrum done" but keep in separate columns.

            Proposed Solution - allow us to configure settings in the PROJECT to classify which Statuses are considered "done" for reporting purposes.  That's it, one configuration item in the project that allows us to say... treat status "READY" and "DOCU" and "DONE" as "done for reporting purposes".

            There are numerous discussions about this topic in discussions... several hacks and at least one product addon that attempts to workaround this.  Here is one and there are several linked to it on the right side nav.
            https://community.atlassian.com/t5/Jira-Software-questions/How-to-configure-the-burndown-chart/qaq-p/1269244

            Bruce Kibbey added a comment - Commenting here in the hopes that it bumps awareness of this. Core issue - BurnUp/ BurnDown reports rely on the LAST COLUMN of the board Debate against - Scrum purists will declare that nothing is done until it hits the last column, anything else isn't scrum, right right. Debate for - Scrum is rarely pure and especially for smaller teams like mine, we have columns for testing and documentation that we'd like to consider as "Scrum done" but keep in separate columns. Proposed Solution - allow us to configure settings in the PROJECT to classify which Statuses are considered "done" for reporting purposes.  That's it, one configuration item in the project that allows us to say... treat status "READY" and "DOCU" and "DONE" as "done for reporting purposes". There are numerous discussions about this topic in discussions... several hacks and at least one product addon that attempts to workaround this.  Here is one and there are several linked to it on the right side nav. https://community.atlassian.com/t5/Jira-Software-questions/How-to-configure-the-burndown-chart/qaq-p/1269244

              Unassigned Unassigned
              htemp Heitor T (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: