Implement automatic reconciling of a successful gated check-in to workspace. We have problems because developers forget to do this and the file stay checked out for months! It would be nice to have this a bit cleaner.

Please add server-side git hooks. Github has this feature and it is extremely useful.

More info here: http://git-scm.com/book/en/Customizing-Git-Git-Hooks#Server-Side-Hooks

Provide TFS with local/offline source versioning option. This will help coders to maintain versioning for offline projects.
Also it will help in scenarios where coder has to edit a large chunk of code in large number of files and he wants to diff between the changes he made in last 1 hr. Without having any shelve or chekin currently they cannot do it. but if they have local version they can create local shelve every 1 hr (also u can provide auto version mode option etc in that which we take versions of code at each 1 hr)

When checking in Pending Changes, it would be useful if there was Intellisense in the Comment textbox.
For example, in TortoiseSVN (and probably others), while typeing the start of a filename/classname/property/method/... that is in your pending changes, a dropdown will appear.
This makes for quicker and easier (and more correct) input of comments.

As a TFS administrator over several servers and hundreds of users I often need to notify end users via email about upcoming system downtime, etc. Presently there is no built-in mechansim to do this and it would be nice to have one. Manually entering hundreds of emails in Outlook isn't an option and I don't think we should have to develop our own app via TFS API to do something like this. It should be a feature of TFS IMO.

Now in our business scenario we need to use a to list and a cc list which we are unable to do.

Actually, there is no easy way to precisely identify the changeset from which a branch has been created.
We can view the hierarchy of course but not the starting point without perform a sql query in the project collection database.

Would Like a feature that makes it easier to move incomplete stories between sprints. For example, I would like to highlight a story on the current sprint and have it copied to a future sprint, but leave the original story intact for historical reasons. Also, all incomplete tasks should be moved forward as well. Currently, if you move a story between sprints, this is not tracked in the history and you can not show what as completed in the past sprints.

TFS Power Tool allows the user to customize a work item, but scope of that customized work items are limited to only that project collection.

I suggest, The user should be able to customize any work items and have the customized work items available across the TFS Projects.

Add a feature to trace all checkins in one preview which is linked to a work item.

For example:- I have multiple checkins for a given task or workticket.
I want to see all changes(as if the checkin was just one) with respect to this task/work ticket in one shot without going through all chain sets.

This will help a lot for review and development.

Users gets an alert if they created an item and that item is changed. it's not possible to configure the alert so that if only the backlog item priority changed (in backlog list, not in current sprint) - ignore it. that happens very often if the product owner reorders the current backlog items

Using Team Foundation Service, Scrum 2.0.

A Product Backlog Item (PBI) can be marked as Done, even when the child tasks it is linked to are In Progress.

I understand there could be a discussion around Definition of Done here, but I think it would be a better experience if an error message or warning was shown.

This would be more in line with what happens elsewhere in Team Foundation Service. For example, when a Task is moved from Done to In Progress ... an elegant message appears, a great experience!

This appears to be a feature that is not in the TFS web service yet.

Allow creation of work items on behalf of another user. For example, when a someone on the developer team receives an email or phone call reporting a problem, or wanting a change, they should be able to create the work item for that user and not have to tell the user they have to raise their own work item.

We have a certain work item type ("Quality Checkpoint") that acts as a gate, and should only be created and edited by people in the QAManager role. Other users (developers, testers, etc.) should be able to open and read the work item but not save any changes to it. I can add role based security on individual fields using the READONLY attribute, but this work item type has hundreds of fields. It would be both tedious and brittle to make every field read-only based on role.

Currently the build agent writes a message like:
"The Fixed In field was updated as part of associating work items with the build."

You should be able to change that message.