Prior to VSTS we have utilized MS Project for our project plans and used the built in ability to create a hierarchy/grouping of tasks.

For example:

+Enhancement #1
+Design
- Complete Requirements doc (actual task)
- Complete Design doc (actual task)
+Implementation
- Complete database functionality (actual task)
- Complete business layer components (actual task)

I have been able to create an equivalent ms project file in an existing Team System project and simply mark the parent items not to publish to team system.

The example above would then create 4 work items in TFS with the Task Context field representing the MS Project hierarchy.

Work Item: Complete Requirements Doc
Task Context: Enhancement #1\Design\

Work Item: Complete Database functionality
Task Context: Enhancement #1\Implementation\

etc...

I would like to be able to customize a new process template by defining default work items and creating a default project plan. I have been able to populate an MS Project file by specifying the QueryID in the WorkItems.xml. I have also been able to specify a default Task Context in each of the default tasks that are created in the template.

The problem (and therfore question) is that when the new project is created in TFS the MS Project file is automatically populated with the work items from the specified query, however the Task Context is not part of the project file. The project file simply lists the work items in a flat structure.

Is there a way to auto populate an MS Project file with the hierarchical Task Context upon project creation?

I don't believe so. Improvements in work item hierarchies and interactions with Project's hierarchies are being investigated now.

Brian