How to fix a burndown chart ruined by a task with an accidentally high number of story points

John DeFilippi

One of the developers on my team added a task with 99999 story points to our sprint.  Now the burndown chart is useless because all it shows is a giant spike that dwarfs all other tasks.  I changed the task to 1 story point, but the burndown chart just looks like a massive rectangle that goes up when the task was added, and goes back down when the task was reduced to 1 story point.  I even removed the task from the sprint, but the history in the burndown chart doesn't change.  How can I fix this?

Simple Tyler

Hey John,

You could try creating a new Sprint, adding in all of your issues and then backdating the start date to your original timeframe.

Not sure if the Burndown would reflect correctly still, but it wouldn't have your huge spike.

Hope this helps,

Tyler