| title | Work Item Fields For Agile and Scrum Processes |
|---|---|
| titleSuffix | Azure Boards |
| description | Explore the default and system work item fields used by the Agile and Scrum processes and process templates for Azure Boards and Azure DevOps. |
| ms.custom | work-items, engagement-fy23 |
| ms.service | azure-devops-boards |
| ms.assetid | 9720b88e-474c-451b-b3fe-5253ba24a653 |
| ms.topic | concept-article |
| ms.author | chcomley |
| author | chcomley |
| monikerRange | <= azure-devops |
| ms.date | 07/22/2025 |
[!INCLUDE version-lt-eq-azure-devops]
This article provides an index of fields used by the Agile and Scrum processes and process templates for Azure Boards and Azure DevOps. The reference covers all default fields and system work item fields defined within the core system processes and templates:
The fields and work item types (WITs) available to you depend on the process you select when you create your project.
::: moniker range="azure-devops"
To support other tracking needs, define your own custom work item fields.
::: moniker-end ::: moniker range="< azure-devops"
To support other tracking needs, define your own custom work item fields by using the Inheritance process model. If your project collection uses the On-premises XML process model, see Add or modify a field for work tracking.
::: moniker-end
Note
The Analytics Service doesn't support reporting on plain text and HTML fields.
The alphabetical index of fields uses annotations to denote the following criteria about the fields:
- (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
- (1) - Available in Azure DevOps Services and Azure DevOps Server 2020 and later versions
- (2) - Available in Azure DevOps Services only
- (3) - Not used by the Agile and Scrum processes or Azure Boards and Azure DevOps
:::row::: :::column span="1":::
- Acceptance Criteria (Scrum)
- Accepted By
- Accepted Date
- Activated By
- Activated Date
- Activity
- Actual Attendee 1-8 (CMMI)
- Analysis (CMMI)
- Application Launch Instructions
- Application Start Information
- Application Type
- Area ID (System)
- Area Path (System)
- Assigned To
- Associated Context
- Associated Context Code
- Associated Context Owner
- Associated Context Type
- Attached File Count
- Authorized As (3)
- Automated Test ID (TCM)
- Automated Test Name (TCM)
- Automated Test Storage (TCM)
- Automated Test Type (TCM)
- AutomatedTestId (TCM)
- AutomatedTestName (TCM)
- Automation Status (TCM)
- Called By (CMMI)
- Called Date (CMMI)
- Changed By (System)
- Changed Date (System)
- Closed By (System)
- Closed Date (System)
- Closed Status
- Closed Status Code
- Closing Comments
- Comment Count
- Comments (CMMI)
- Committed (CMMI)
- Completed Work
- Contingency Plan (CMMI)
- Corrective Action Actual Resolution (CMMI)
- Corrective Action Plan (CMMI)
- Created By (System)
- Created Date (System)
:::column-end::: :::column span="1":::
- Discipline (CMMI)
- Description (System)
- Due Date
- Effort
- Escalate (CMMI)
- External Link Count
- Finish Date
- Found In Build (TCM)
- Found In Environment (CMMI)
- History (System)
- How Found (CMMI)
- Hyperlink Count
- ID (System)
- Impact Assessment (CMMI)
- Impact on Architecture (CMMI)
- Impact on Development (CMMI)
- Impact on Technical Publications (CMMI)
- Impact on Test (CMMI)
- Impact on User Experience (CMMI)
- Integrated in Build (TCM)
- Issue (TCM)
- Iteration ID (System)
- Iteration Path (System)
- Justification (CMMI)
- Link Comment (System)
- Link Description (System)
- Local Data Source (TCM)
- LocalDataSource (TCM)
- Meeting Type (CMMI)
- Minutes (CMMI)
- Mitigation Plan (CMMI)
- Mitigation Triggers (CMMI)
- Node Name (System)
- Optional Attendee 1-8 (CMMI)
- Original Estimate
- Parameters (TCM)
- Parent (1)
- Priority
- Probability (CMMI)
- Proposed Fix (CMMI)
- Purpose (CMMI)
- Query Text (TCM)
:::column-end::: :::column span="1":::
- Rating
- Reason (System)
- Related Link Count (System)
- Remaining Work
- Remote Link Count (System) (2)
- Repro Steps
- Required Attendee 1-8 (CMMI)
- Requirement Type (CMMI)
- Requires Review (CMMI)
- Requires Test (CMMI)
- Resolution (Scrum)
- Resolved By
- Resolved Date
- Resolved Reason
- Rev (System)
- Reviewed By
- Reviewed Date
- Revised Date (System, TCM)
- Risk (Agile)
- Root Cause (CMMI)
- Severity
- Size (CMMI)
- Stack Rank
- Start Date
- State (System)
- State Changed Date
- State Code
- Steps (TCM)
- Steps to Reproduce (TCM)
- Story Points (Agile)
- Subject Matter Expert (CMMI)
- Symptom (CMMI)
- System Info (TCM)
- Tags
- Target Date
- Target Resolve Date (CMMI)
- Task Type (CMMI)
- Team Project (System)
- Test Suite Audit (TCM)
- Test Suite Type (TCM)
- Test Suite Type ID (TCM)
- Time Criticality
- Title (System)
- Triage (CMMI)
- User Acceptance Test (CMMI)
- Value Area
- Watermark (System)
- Work Item Type (System)
:::column-end::: :::row-end:::
Use system fields or custom fields added to your project collection and enable meaningful cross-project reports and queries. Any nonsystem field referenced in the workflow or forms section of the work item type definition must have a FIELD element defined in the FIELDS section of the work item type definition XML file. Specify any nonsystem field you want to use for generating queries or reports in the FIELDS section.
The following articles describe fields that are commonly used by several work item types or are functionally specific to one or a few WITs. For more information, see Work item fields and attributes in Azure Boards.