Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-10261

Burndown based on status

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Answered
    • None

    • 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.

      It would be great if we can customize the burndown dependency.
      So far, the burndown is based on the rightmost column of the board, which is not so convenient for some scenarios.
      What we need is that the burndown definition can be independent from the column mapping and customizable to base on a specific status / resolution.

            [JSWCLOUD-10261] Burndown based on status

            Laura added a comment -

            +1

            Laura added a comment - +1

            Will Floutier added a comment -

            +1

            Will Floutier added a comment - +1

            James Gollan added a comment -

            +1

            James Gollan added a comment - +1

            Radu Lupu added a comment -

            +1

            Radu Lupu added a comment - +1

            Tim Bodeit added a comment -

            Everybody who is +1-ing this Issue: Make sure to upvote GHS-12169

            Tim Bodeit added a comment - Everybody who is +1-ing this Issue: Make sure to upvote GHS-12169

            Peter Kazmir added a comment -

            +1 for reopening this. The "solution" is not very usable. I don't want to have, in effect, two different burndown charts. I want to either be able to customize the burndown chart so it keys off of whatever column/state I want it to, or I want to be able to mark a specific column as "done".

            I have exactly the same scenario as many others have described: I have a state called "Done" and a state called "Accepted". The team gets "credit" in their burndown when the story is Done (i.e. ready for sprint review/acceptance), but the story isn't really complete until it has been reviewed and accepted. And I don't want to put both Done and Accepted in the same column.

            Peter Kazmir added a comment - +1 for reopening this. The "solution" is not very usable. I don't want to have, in effect, two different burndown charts. I want to either be able to customize the burndown chart so it keys off of whatever column/state I want it to, or I want to be able to mark a specific column as "done". I have exactly the same scenario as many others have described: I have a state called "Done" and a state called "Accepted". The team gets "credit" in their burndown when the story is Done (i.e. ready for sprint review/acceptance), but the story isn't really complete until it has been reviewed and accepted. And I don't want to put both Done and Accepted in the same column.

            Ross McKenrick added a comment -

            +1 for reopening

            Ross McKenrick added a comment - +1 for reopening

            Dory Weiss added a comment - - edited

            +1 for reopening

            Dory Weiss added a comment - - edited +1 for reopening

            Duncan Fletcher added a comment -

            +1
            Another example of Atlassian knowing best?

            Duncan Fletcher added a comment - +1 Another example of Atlassian knowing best?

            Theo van den Bogaart added a comment -

            +1 there should be a possibility to have multiple states result in a Burndown event when moving from a non-done state to a done state and vice vera.

            Theo van den Bogaart added a comment - +1 there should be a possibility to have multiple states result in a Burndown event when moving from a non-done state to a done state and vice vera.

              Unassigned Unassigned
              aquadrospetry Andre Quadros Petry (Inactive)
              Votes:
              5 Vote for this issue
              Watchers:
              33 Start watching this issue

                Created:
                Updated:
                Resolved: