Thus, we discovered and completed 18 hours of work that we didn't realize were there.
I would expect the entire burndown to "shift up", have it recalculate based on 218 hours total, and we would now be at 100.
Does anyone know where it gets the data for this burn down? After a bit of debugging I noticed that in the function above it returns the of the split var t incorrectly ...
some of the dates passed to this function have the full UTC format with T and Z in them (i.e.
2012-11-02TZ) perhaps it is this split that is not working correctly and hence passing invalid dates in the data for highcarts? Now I have to look for solution to the tasks's tab problem.
I don't have time to spend on fiddling with it but perhaps this might give someone some idea aqwerf's solution worked for me too!
This doesn't quite make sense to me--the upshot is, if I create a task today and finish it today, no hours are burned; but, if I create a task today, work on it today, and finish it tomorrow, then some but not all of its hours burn. So you can trust the prediction (which is the most important piece of the burndown), but you cannot see exactly how much work was done each day (which scrum cares a lot less about).
There are a number of User Voice tickets on this and a there might be bugs files on connect. I agree the last day of the burndown will be correct, but the burndown on individual days is wrong, as it will show no work completed for such created and worked-on tasks.
Review your sprint burndown chart throughout your sprint cycle to check for these indicators: The system automatically builds a sprint burndown chart based on the tasks and Remaining Work estimates you define and update throughout the sprint cycle. To open the sprint burndown chart, jump to the section Open sprint burndown chart.
I mention that the sprint started today 31/10/2016 and it will finish sunday, 6/11/2016. Can someone please explain why the chart starts from 60 as remaining hours instead of 80? If your today(10/31) did nothing, the actual graph, the blue area should start from 80 not 60.
If your today(10/31) did 30 capticy,the blue area should start from 50.
As explained in this blog post ( we had updated the status of this suggestion to “Under Review” to let you know we are tracking it on our backlog.
To better indicate which one we are actively working on or which ones are on our 6-month plan, we introduced the states “Started” and “Planned”.