| title | titleSuffix | description | ms.custom | ms.technology | ms.assetid | ms.topic | ms.author | author | monikerRange | ms.date |
|---|---|---|---|---|---|---|---|---|---|---|
Index of default and system work item fields |
Azure Boards |
Index to all fields used in the Agile, Scrum, and CMMI processes/process templates for Azure Boards, Azure DevOps, & Team Foundation Server |
work-items |
devops-agile |
9720b88e-474c-451b-b3fe-5253ba24a653 |
conceptual |
kaelli |
KathrynEE |
>= tfs-2013 |
07/09/2020 |
[!INCLUDE temp]
Use this index to look up a description of each field used to track work items. This reference includes all fields defined within the core system processes/process templates: Basic, Agile, Scrum, and CMMI. The fields and work item types (WITs) available to you depend on the process you chose when you created your project.
::: moniker range="azure-devops"
To support additional tracking needs, you can define your own custom work item fields.
::: moniker-end
::: moniker range=">= azure-devops-2019 < azure-devops"
To support additional tracking needs, you can define your own custom work item fields using the Inheritance process model, or if your project collection is configured to use the On-premises XML process model, then see Modify or add a custom field.
::: moniker-end
::: moniker range="<= tfs-2018"
To support additional tracking needs, you can modify or add a custom field.
::: moniker-end
::: moniker range=">= azure-devops-2019"
Note
The Analytics Service doesn't support reporting on plain text and HTML fields at this time.
::: moniker-end
Values in parenthesis indicate the following:
- System: Core system field assigned to all work item types for all processes
- Agile: Used only by the Agile process
- CMMI: Used only by the CMMI process
- Scrum: Used only by the Scrum process
- TCM: Used to support Test case management
- These fields are available from Azure DevOps Services and TFS 2015.1 or later versions.
- The Comment Count field is available from Azure DevOps Services and TFS 2017 or later versions.
- These fields are available from Azure DevOps Services and Azure DevOps Server 2020.
- These fields are available from Azure DevOps Services only.
By using the system fields or other fields you have added to your project collection, you can enable meaningful cross-project reports and queries. In addition, any non-system field that is referenced in the workflow or forms section of the work item type definition must have a FIELD element that defines it in the FIELDS section of the work item type definition XML file. Also, you must specify any non-system field that you might want to use to generate a query or report in the FIELDS section.
The following articles describe fields that are used in common by several WITs, or those that are functionally specific to just one or a few WITs.
- Titles, IDs, and descriptive fields
- History and revision changes
- Areas and iterations
- Assignments and account-specific fields
- Planning, ranking, and priorities
- Work estimates, activity, and other numeric fields
- Build and test integration fields
- Links and attachment related fields
- About work item fields
- About managed queries
- Define a query
- Choose a process
- Reportable fields reference (on-premises Azure DevOps only)