TFS(ervice) Burndown chart - First day work did not get reflected in Burndown chart - by Wayne Shaw

Status : 

  By Design<br /><br />
		The product team believes this item works according to its intended design.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 788378 Comments
Status Closed Workarounds
Type Bug Repros 2
Opened 5/22/2013 4:55:39 AM
Access Restriction Public


Working on a Team Foundation Service 2012 project. The iteration start and end dates created in the system were (are) 14th May to the 6th of June, a 4 week sprint. On the 13th of May we had our review meeting and created all of the tasks in the application and the total commitment for the iteration was 318 hours. This was shown on the home screen and the burn down chart correctly at the end of the 13th of May and the actual start of the iteration on morning of the 14th of May. 

However, on the 14th of May when tasks where being completed the starting point of the burn down was coming down rather than staying at 318 and the bar moving down in a downward fashion. Only on the second day this started working correctly however from the burndown it looks like we actually started on 285 hours rather than 318 looking like we actually commited to the 285 hours rather then the 318. 

In our first iteration (16th April to the 9th May) the burnchart looked correct as it started with the bar chart coming out to display the first days work. 

Sign in to post a comment.
Posted by Microsoft on 5/28/2013 at 9:43 AM
This is expected behavior. To draw an area on a chart, you need to have at least two days of data. We have heard this request more often and are looking in ways how to address this in the future.
Posted by Microsoft on 5/23/2013 at 12:04 AM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 5/22/2013 at 12:53 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(