Add Type Definitions for Work Item Categories to a Process Template

You can add categories to your process template. A category associates a group label with one or more types of work items. Categories are useful when your team projects contain similar work item types that are named differently. You specify the category definitions in one file, and then you specify that file to upload within the taskxml element of the WorkItemTracking plug-in.

Important noteImportant

The process templates for Microsoft Solutions Framework (MSF) v5.0 define four categories that are useful for test case management. For more information, see Working with Work Item Type Categories.

In this topic

After a team project is created from the process template, you can export and import categories for a team project collection by using the witadmin command-line tool. For more information, see Customizing Categories for Work Item Types [witadmin].

The file that defines the categories must conform to the schema definition for categories, defined in the categories-01.xsd file, and must be specified in its own file in the WITD container element. You can download the schema files for tracking work from the following page on the Microsoft website: Process Template and Work Item Schemas for Visual Studio Team Foundation.

The following example shows the syntax structure that defines a category that is named Requirement Category and that is associated with the User Story work item type.

   <CATEGORY refname="Microsoft.RequirementCategory" name="Requirement Category">
      <DEFAULTWORKITEMTYPE name="User Story" />
   . . . 

You can customize or create a category definition file. For the MSF process templates, the category file is defined in the WorkItem Tracking folder. For more information about how to define categories, see Grouping Work Item Types into Categories.

Back to top

To upload a set of category definitions, you specify the CATEGORIES element within the taskxml element. The filename attribute is a relative path of the category definition file. For example, the following syntax specifies that the categories.xml file will be uploaded.

<CATEGORIES fileName="WorkItem Tracking\categories.xml" />

The following example shows how to specify a task that uploads a categories file. Because each category specifies a default work item type, the task to upload the category definition file depends on the successful completion of the WITs task which uploads the type definitions for work items.

<task id="Categories" name="Categories definitions" plugin="Microsoft.ProjectCreationWizard.WorkItemTracking" completionMessage="Work item type categories created">
      <dependency taskId="WITs" />
      <CATEGORIES fileName="WorkItem Tracking\Categories.xml" />

Back to top

The following table describes the CATEGORIES element that you use to upload the category definition file. You specify this element within a taskXml container element in the WorkItemTracking plug-in file.


You specify a definition file to upload using the CATEGORIES (WorkItemTracking) element. You specify the set of categories to define using the CATEGORIES (Definition) element. For more information, see Working with Work Item Type Categories





<CATEGORIES fileName="CategoriesFilePathName" />

Optional child element of the WorkItemTracking plug-in.

Specifies the path and name of the file that contains the category definitions to be uploaded when the WorkItemTracking plug-in task is processed.

Back to top

Community Additions