Field descriptions for default and work item fields used in process templates
TFS 2018
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.
To support other tracking needs, you can modify or add a custom field.
Values in parenthesis indicate the following criteria:
- 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
A
- 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 (Not used)
- Automated Test ID (TCM)
- Automated Test Name (TCM)
- Automated Test Storage (TCM)
- Automated Test Type (TCM)
- AutomatedTestId (TCM)
- AutomatedTestName (TCM)
- Automation Status (TCM)
B
C
- Called By (CMMI)
- Called Date (CMMI)
- Changed By (System)
- Changed Date (System)
- Closed By (System)
- Closed Date (System)
- Closed Status
- Closed Status Code
- Closing Comment
- 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)
D-E-F
- Discipline (CMMI)
- Description (System)
- Due Date
- Effort
- Escalate (CMMI)
- External Link Count
- Finish Date
- Found In Build (TCM)
- Found In Environment (CMMI)
H
- History (System)
- How Found (CMMI)
- Hyperlink Count
I
- 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)
J-L-M-N
- Justification (CMMI)
- Link Comment (System)
- Link Description (System)
- Local Data Source (TCM)
- Meeting Type (CMMI)
- Minutes (CMMI)
- Mitigation Plan (CMMI)
- Mitigation Triggers (CMMI)
- Node Name (System)
O-P-Q
- Optional Attendee 1-8 (CMMI)
- Original Estimate
- Parameters (TCM)
- Priority
- Probability (CMMI)
- Proposed Fix (CMMI)
- Purpose (CMMI)
- Query Text (TCM)
R
- Rating
- Reason (System)
- Related Link Count (System)
- Remaining Work
- Remote Link Count2 (System)
- 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)
S
- Severity
- Size (CMMI)
- Stack Rank
- Start Date
- State (System)
- State Change Date
- State Code
- Steps (TCM)
- Steps to Reproduce (TCM)
- Story Points (Agile)
- Subject Matter Expert (CMMI)
- Symptom (CMMI)
- System Info (TCM)
T
- 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)
U-V-W
- User Acceptance Test (CMMI)
- Value Area
- Watermark (System)
- Work Item Type (System)
Note
- This field is available from Azure DevOps Services and Azure DevOps Server 2020 and later versions.
- This field is available for Azure DevOps Services only.
Using the system fields or other fields you added to your project collection, you can enable meaningful cross-project reports and queries. Also, any nonsystem 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 nonsystem 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 fields 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
- About processes and process templates
- Reportable fields reference (On-premises XML process model only)