Sprint Burndown Chart - Shouldn't consider estimates from removed tickets

XMLWordPrintable

    • 2

      The Story Point estimate for one story in the sprint was originally set a very high value  276,447,231 , the impact of this entry is that it messes the Sprint Burndown chart as it only shows a single vertical line representing  a very high value reflecting the remaining estimate at the time.  Even removing this ticket from the Sprint didn't fix the burdnown chart.

      One accidental entry impacts the Sprint burndown chart and there is no way to fix the chart. 

              Assignee:
              Unassigned
              Reporter:
              Jacob Thomas
              Votes:
              2 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: