Almost daily I try to check in some pending changes. I enter a comment, because it is required by our TFS server. I might spend 2 or 3 minutes writing a very detailed comment describing all of the changes and why I am making them. When I press "Check In" I get a dialog stating that there are conflicts. I resolve the conflicts and now what... Nothing. I have to press "check in pending changes" again. My comment is lost. I have to write it over again. Another 3 minutes re-writing the comment and some frustration go by, then I click "Check In" again. Shew! No problems.

Many IDEs for Subversion and CVS save our comments to a local cache so that they can be reused, especially in cases like this. In other cases I need to use the same comment for multiple check-ins. There is usually a select box listing the previous comments. I select a previous comment and the text area is populated with the previous text. From there I can modify the text area and then press "Check In".

This would be a great feature I think.

I would like to have the ability to Customize WorkItemChangedEvent so when WI is changes, the mail notification will include also predefined customized fields in addition to the predefined core fields it currently supports.
Today, the following core fields are included in every notification mail: Team Project, Area, Iteration, Assigned To, State, Reason, Changed By and Changed Date.
Customize field is included in the mail only when it is changed, this is the default behaiver of the TFS.
We would like to have this field in all notification mails, even when not changed.
For example, the customized field for the Project Account: When getting mail notification on a change in a Bug WI, I want to know which is the account without the need to enter the system (required especially cause we all use mobile smartphones).

Force the TFS team to completely end-to-end manage a release, SP or something via TFS out of the box as is. In reading the items in this list (other than plug-ins), nearly all of the items below show that people are just trying to use it, as it was probably intended. Its a great product, AWESOME in fact, but lacks so many basic items (all listed here), renaming a project, really?, and the only thing I can come up with is becuase the team just doesn't really use it out of the box with minimal customization (or if they do, they're not allowed to voice their opinions)... no team would put out a product and not include the Checkbox for the editor portion release after release if they really wanted people to use boolean values... I can set up complex rules, but for boolean its YES/NO?

So please make the team commit to release a version, an SP, a something using the default settings. Atleast half of these items would then be on the list from them. Really, is the real world scenario they invisioned, Not Done, In Progress, Done (no ready for test, or staging concept, or tested, is it really what's done is done?) TPE... visio and WF have pretty good designers, TPE... a little more sub-par.

If this was being used default out of the box by the team then nearlly all of these would JUMP out at them.

think about how awesome it would, "we use it and we saw these issues, do you agree? if so vote for them so we'll take them more seriously", instead, its more like "tell us our problems and vote them". No, the problems are so obvious, you guys take a stab at them first to showing how much you care, we'll vote and add the ones you've forgotten. :)

We are a small development team, moving very quickly on a new product. It would be interesting if we could enable a "Continuous Get Latest" feature.
The idea is: when one developer checks in a change, all all other developers currently working on that solution (on that branch) would be automatically updated with the source (in Visual Studio), in real-time, with no action required.
A few seconds delay would be good, but even a minute is probably OK.

This would save us from having to yell "Finished {feature/change here}, everyone update latest!" over the cubes and keep us more tightly integrated.