1,414 votes49 comments · Visual Studio » Team Foundation Server & Visual Studio Online · Flag idea as inappropriate… · Admin →
The problem with all of the pluggable version control system ideas was mentioned by one comment in this thread. TFS != Version Control alone. TFS' work item to code traceability is one of its largest strengths. Replacing the version control system is not as easy as it sounds when viewed under that light. Will git build in all the necessary touch points so that changesets can shelvesets can be tracked alongside work items? Will Perforce do this? What about SVN, CVS, Mercurial and Plastic SCM? TFS appeals to our highly regulated company mainly because of the traceability provided out of the box. Work item through to line of code changed. Work under Sarbanes Oxley or HIPPA regulations and you'll see where I and the other guy commenting on work item tracking are coming from. The source control choice isn't simply a geeks prefer to use this choice; it has larger implications for the company as a whole.
This would be a nightmare for transparency. Most of the products asking to be integrated have no love for anything Microsoft. Open Source Sortware comes to mind. Transparency would suffer. Traceability would suffer. How is work shelved and unshelved as tasks move from in progress to todo and back? What analogies need to be mapped between source control systems for shelvesets and changesets? These are fundamental concepts to the entire TFS system working properly. I can't see how CVS, Git, Mercurial, etc., etc. would map consistently unless each product released a TFS version.
64 votes13 comments · Visual Studio » Team Foundation Server & Visual Studio Online · Flag idea as inappropriate… · Admin →
We are not planning to modify the reports that we included in TFS 2010. We will invest in the solution that we have created for TFS 2012, which is the burndown chart on the task board.
Ewald Hofman – TFS Product Group
The option to include or not innclude would be nice. Lots of our work gets done afterhours and by contractors working weekends so I can see use for it both ways. Perhaps have this as a setting on the team and have the burndown report read from the teams working on the project to see if they are working weekends.
187 votes2 comments · Visual Studio » Team Foundation Server & Visual Studio Online · Flag idea as inappropriate… · Admin →
615 votes12 comments · Visual Studio » Team Foundation Server & Visual Studio Online · Flag idea as inappropriate… · Admin →
We completely agree with you all that a checkbox is very valuable to add to our form. I am happy to let you know that we have started to build the checkbox control.
339 votes21 comments · Visual Studio » Team Foundation Server & Visual Studio Online · Flag idea as inappropriate… · Admin →
As mentioned before, we’re not planning to do work in this area so we’re returning your votes. However, there are a couple of alternatives:
Imaginet Timesheet: http://www.imaginet.com/imaginettimesheet
SSW Time Pro: http://www.sswtimepro.com/
Project Server integration.
SCRUM and Agile frameworks do not show time worked. The philosophy of the development methodology is only about what remains to hit the product goal. It's a culture and mind shift to get used to not measuring the water under the bridge. If you need it for consulting work, I suggest you use a timesheet product because TFS is not where you track consultant time. When the goal is to get stuff completed, worrying about how much time was spent to get you where you are today is wasting cycles and energy on a problem in the past.