Home Dashboard Directory Help
Search

Inconsistent/Bad Sprint Burn Down Charts by jdlaw64


Status: 

Resolved
 as Fixed Help for as Fixed


4
0
Sign in
to vote
Type: Bug
ID: 777826
Opened: 1/29/2013 6:10:39 PM
Access Restriction: Public
0
Workaround(s)
view
3
User(s) can reproduce this bug

Description

We are running TFS 2012 Update 1 Patch 1 and have noticed in several projects we have some Sprints that display irratic/bad burn down charts. some appear to change every time you click on them. Yet the Sprint burn down charts displayed in SQL Reports appear to be correct, or at least consistent.

One peculiar thing I've noticed is the sprints that have bad/inconsistent burn down charts displayed in TWA the sprint contains several WI's with state "To Do" yet sprints that appear to have good/accurate/consistent charts ... all WI's reflect state "Done". Not sure if the problem is related to this or not?

Please see below post for additional info and chart examples.

http://social.msdn.microsoft.com/Forums/en-US/tfsgeneral/thread/d3243034-f31d-42a4-a2a6-0dcc05893b79/
Details
Sign in to post a comment.
Posted by Microsoft on 4/29/2014 at 12:29 PM
Thank you for reporting this issue. This issue has been fixed in Visual Studio 2013. You can install a trial version of Visual Studio 2013 with the fix from: http://go.microsoft.com/?linkid=9832436
Posted by Microsoft on 2/5/2013 at 10:50 AM
Sorry you ran into this problem. The behavior that you run into is caused by caching that we added in the burndown chart in VS Update 1. We have a fixed this in VS Update 2, which will be released soon.
Posted by Microsoft on 2/4/2013 at 3:52 AM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Microsoft on 1/29/2013 at 6:50 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.