High-Level Structure of a Work Item Type
A small number of XML elements appear between <WORKITEMTYPE> tags at the highest levels of the work item type definition. You start defining a work item type by providing a name and a description. You also use certain standard XML tags to wrap the work item type definition. The following sample shows the high-level structure of a work item type:
<WITD application="work item type editor" version="1.0"> <WORKITEMTYPE name="bug"> <DESCRIPTION>Bug work item types are used to track defects in the code.</DESCRIPTION> <GLOBALLISTS> </GLOBALLISTS> <FIELDS> </FIELDS> <WORKFLOW> </WORKFLOW> <FORM> </FORM> </WORKITEMTYPE> </WITD>
The structural elements used in the previous example are described here:
<WITD application="work item type editor" version="1.0">
The complete work item type definition is wrapped by the tag <WITD>. You can use any name for the application name. The version identifies the schema of the work item type that changes from one release to the next. Use "1.0."
Work item type names must be unique in a specific team project. This name is used at run time. For example, the name can appear as a menu option. In this case, a user would be able to click Bug on the New Work Item menu. For more information, see.
The description is Help text that can be used at run time when an overview of the work item type in a project is needed. For example, the Help text can explain to a user the difference between a risk and an issue. For more information, see.
The description is only viewable in the XML definition. The description is not visible anywhere in the user interface and has no relationship to the field System.Definition.
Additional topics discuss <GLOBALLISTS>, <FIELDS>, <WORKFLOW>, and <FORM> sections in detail. For more information, see, , , and .