In TFS 2010 we can set permissions on areas and iterations to limit access to work items and queries. However, all TFS users can still see the names of all area and iteration nodes regardless of permissions. There should be permissions that limit the visiblity of area and iteration node names.

Scenario: We use a single team project for development of multiple products for multiple different customers. We configure areas and iterations for each different customer/product and set permissions on those nodes to limit access. Some customers and products are highly confidential and the associated area and iteration names should not be visible TFS users unless they have been granted access.

Also see this post https://connect.microsoft.com/VisualStudio/feedback/details/668013/area-and-iteration-nodes-are-not-hidden-by-permission

In TFS, it’s possible to introduce Custom Link type(s) that can be used to Link up two WorkItem records. Customers that have used Open Source process template like Scrum for Team Systems have used custom links all over the place. Plus this is supported feature within TFS where by it allows customization of Link Types via Process Template Modification. Now, in TFS 2012, in Web based Sprint boards, it only supports Parent / Child link type. It does not support Custom Links which I think is a big gap. Without support for Custom Links I could only see one type of work item within the sprint board.

Microsoft should support custom link to show Requiremtns / Tasks based WorkItems on the Web board as they do allow users to customize Custom Links via Process Template modifications.

Please make it easier to find related work items from the new pending changes view. I would like to see a search box instead of a text box to enter a difficult to remember unique ID. If I absolutely must drag & drop work items to this canvas, then I would like an easier way to open up a work item query without having to navigate away from the pending changes view. I'm surprised this wasn't addressed in the Beta as I can't imagine anyone actually who has used this preferring it to the old way of associating work items with pending changes.

There isn't a good way to group or categorize items on the product backlog at the moment. Especially when starting up a new project, this means the backlog is huge and you'll probably need some sort of way to keep track of everything. There's areas, but those don't show on the product backlog. There's linkin items, but that also affects prioritising in way you don't want it to.

Some kind of tagging system would be nice. Suppose you could tag your workitems with categories (the way SharePoint tagging works is quite powerfull). Those categories could then be used to filter, search or group items on the product backlog. Product owners would be pleased I think, since this makes it a lot easier to keep track of everything.

The current philosophy seems to be that only active team members can participate in code reviews which are always made for one check-in. Here are a few suggestions on how to make it more usable.
1) Make it web-based so one doesn't need Visual Studio (and sources for entire solution). This way one could easily ask for consultancy from a remote expert
2) Make it possible to create review request afterwards and possibly spanning multiple check-ins. The current practise suggests people to do huge check-ins which is not a best practise.
3) Have the comments to make a discussion tree. Currently comments are plain comments and one can't reply to a comment, so a real conversation is not possible using this feature.
4) The process of adding a comment (right click -> add comment -> write -> save (or using shortcuts left mouse click -> ctrl+shift+k -> write -> ctrl+enter) is not as fluent as it could be.
Just clicking the source in code review window could open a new comment box. And a plain enter on this box could save it.

TFS seems to assume that all parties that want to collaborate are on the same network.

We want our customers to be able to raise defects, feature requests, view progress reports etc

Issues we currently face with TFS 2010.

1. Our customers are not on our internal AD and will never be although we would be happy to set up accounts for them in alternate identity store.
2. There does not seem to be a lot of info about exposing TFS to the internet.

I would like to see better support for this scenario. The authentication story at the moment seems rather rigid.