|Important||This document may not represent best practices for current development, links to downloads and other resources may no longer be valid. Current recommended version can be found here.|
Work Item Type Contents
Work item types consist of the following high-level items:
A work item type name that must be unique in a team project. Examples include bug, feature, requirement, risk, and task. For more information, see.
A description is a comment in the XML that describes what the work item type does. The description is used during work item type customization to describe the work item type to the person making changes to the work item type definition XML file. For more information, see.
A list of fields that defines the relevant set of fields for the work item type. The field definition is global to a Team Foundation Server. Every work item type contains a set of system fields that are required for every work item type. For more information, seeand .
A workflow definition that defines the set of valid states, valid transitions between those states, and what users or groups have permission to perform these transitions. For more information, seeand .
A set of field rules that define the business rules for fields and field values as the work item moves through its state transitions. For more information, see.
A form that defines how the relevant fields are displayed and manipulated by the users. For more information, seeand .
Work item types also might define or reference a set of global lists that are named lists of values that might be re-used across team projects and work item types. For more information, seeand .