You can see right click menu items for the obvious things you\u2019d like to do, add a new child, outdent, indent, etc.<\/p>\n
<\/p>\n Microsoft Excel integration has also been enhanced to support work item hierarchies as well\u2026 As you can see, we use multiple \u201cTitle\u201d columns to represent the hierarchy level in Excel. You can also see some of the new Tree features in the ribbon.<\/p>\n And lastly, the hierarchy round trips with Microsoft Project as well\u2026 As you can see here, Project can also be used as a roll up engine to compute rolled up schedule numbers. In previous versions of TFS, the project hierarchy was only persisted in the MS Project file so TFS users couldn\u2019t see the hierarchical relationships.<\/p>\n We have added the ability to define custom link types in TFS 2010. In previous version there was really only one work item to work item link type called \u201crelated\u201d. Now you can define your own link types that can be used in querying and reporting (see more on querying in the next section). As an example, as part of the new TFS base process templates, we\u2019ve added a link type called Tests\/Tested By. It is defined to relate a test case and a user story and identifies the set of test cases for a user story. However, you can define your own with whatever semantics you choose.<\/p>\n When you create a link type, you can define one of 4 link \u201ctopologies\u201d:<\/p>\n Now that we have custom link types you can do some very cool stuff with traceability. The reporting system always allowed you to report on links but now you can filter by link type and Team Explorer and Team System Web Access also enable querying on links. So using the test case tests user story link I mentioned above, here\u2019s a sample query in Team Explorer. Notice that the Type of Query combo now says Work Items and Direct Links. Also, notice that the query definition has a lot more filters. Following the grid that selects User Stories, there\u2019s another grid that selects how you want to filter what the matched user stories are linked to (Test Cases that are not closed, in this example). In the linking filters you have 3 main options:<\/p>\n And finally, you can filter by one or more link types. You can see by my query results that my sample project has 3 user stories, 2 of which each have one test case.<\/p>\n And, of course, all of this works in Web Access as well, but just to prove it, a picture is worth a thousand words\u2026<\/p>\n Now that relationships between work items are playing a more first class role in the system it seems obvious you are going to want to do more with them on the work item form itself\u2026 enter the new work item form links control. Here are the characteristics of it:<\/p>\n So on with a screenshot. Here\u2019s an example of the Test Cases tab on a User Story work item.<\/p>\n There are a bunch of other work item control improvements in addition to the links control. They include:<\/p>\n In previous versions of TFS, work item query clauses could only compare a field against a constant. In 2010, they can now compare fields with each other. So, for example, if I wanted to find all tasks where the Completed Work is greater than the Original Estimate, I could do this\u2026 I suspect you\u2019ll be able to think of lots of novel ways to use this. We ran across the requirement when building our Project Server integration and try to find a way to easily identify work items where the project manager rejected cost changes made by the developer.<\/p>\n <\/p>\n <\/p>\n <\/p>\n It\u2019s now possible to easily write queries that filter by groups of people. TFS has always had the ability to synchronize with Active Directory to import group information. Now you can write queries that enable you to easily filter by group membership. For example, I could write a query to find all work assigned to \u201cMy team\u201d like this\u2026<\/p>\n Query Folders<\/strong><\/p>\n The more powerful we make queries, the more of them you want to have \u2013 and that means you are going to need a way to organize them. Also we\u2019ve gotten a lot of feedback that people would like a better way to publish queries without having to be a Project Administrator (you have to be to save a Team Query in TFS 2008 and before). We solved both problems with a new feature called query folders. This allows you to organize your queries into folders both under My Queries and under Team Queries. Further, under Team Queries, you can delegate permissions to the sub folders to whomever you like. In the screenshot below you can see a query structure I\u2019ve created a the security dialog where I\u2019ve granted the Contributors group permission to contribute queries to the Web Team folder. I know this is going to be a VERY popular feature internally where we get dozens, if not hundreds, of queries people want to share.<\/p>\n We\u2019ve made a number of small work item tracking usability improvements. I don\u2019t think I can even remember them all but I\u2019ll mention a few.<\/p>\n We\u2019ve added several controls to improve your options for managing layout for your work item tracking windows. Looking at this screenshot, you will see 4 small controls on the right hand side of the splitter bar between the results list and the work item form. The first two switch back and forth between a horizontal split and a vertical split.<\/p>\n like this\u2026<\/p>\n <\/p>\n The second two make it simple to \u201cmaximize\u201d either the work item form or the results list, like\u2026<\/p>\n![\"image\"](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/8\/2019\/02\/image_4.png\" "\\"image\\"")
<\/a> <\/p>\n<\/a> <\/p>\n<\/a> <\/p>\nCustom link types<\/h3>\n
\n
Link Queries<\/h3>\n
\n
<\/a> <\/p>\n<\/a> <\/p>\nNew links control<\/h3>\n
\n
<\/a> <\/p>\nOther new work item controls and improvements<\/h3>\n
\n
Field comparison queries<\/h3>\n
<\/a> <\/p>\nGroup membership queries<\/h3>\n
<\/a> <\/p>\n<\/a> <\/p>\nUsability improvements<\/h3>\n
<\/a> <\/p>\n<\/a> <\/p>\n