Work item field index

VSTS | TFS 2018 | TFS 2017 | TFS 2015 | TFS 2013

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: 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 additional tracking needs, you can define your own custom work item fields. For more information, see:

Alphabetical index

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
A through C D through Q R through W
- 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)
- Backlog Priority (Scrum)
- Blocked
- Board Column
- Board Column Done
- Board Lane
- Business Value
- 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
- Comments (CMMI)
- Committed (CMMI)
- Completed Work
- Contingency Plan (CMMI)
- Corrective Action Actual Resolution (CMMI)
- Corrective Action Plan (CMMI)
- Created By (System)
- Created Date (System)
- Discipline (CMMI)
- Description (System)
- Due Date (Agile)
- Effort (Scrum)
- 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)
- 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)
- Rating
- Reason (System)
- Related Link Count (System)
- Remaining Work
- Repro Steps
- Required Attendee 1-8 (CMMI)
- Requirement Type (CMMI)
- Requires Review (CMMI)
- Requires Test (CMMI)
- Resolution] (Scrum)
- Resolved By
- Resolved Date
- Resolved Reason
- Reviewed By
- Reviewed Date
- Rev (System)
- Risk (Agile)
- Root Cause (CMMI)
- 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 1-3 (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)
U - V - W
- User Acceptance Test (CMMI)
- Value Area
- Work Item Type (System)

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.

Field reference topics

The following topics describe fields that are used in common by several WITs, or those that are functionally specific to just one or a few WITs.

What is a field? How are field names used?

A work item field name uniquely identifies each work item field. Make sure your field names fall within these guidelines:

  • Field names must be unique within the account/project collection
  • Field names must be 128 or fewer Unicode characters
  • Field names can't contain any leading or trailing spaces, nor two or more consecutive spaces
  • Field names must contain at least one alphabetic character
  • Field names can't contain the following characters: .,;'`:~\/\*|?"&%$!+=()[]{}<>.

Because custom fields are defined for the account collection, you can't add a custom field to a process with the same field name that you add to another inherited process.

When adding custom fields, note the following limits:

  • A maximum of 256 fields can be defined for each WIT
  • A maximum of 512 fields can be defined per process

Hidden field attributes and the Work Item Field Explorer

There are several non-changeable and virtually hidden attributes for each field. You can look up the assignments of these fields using the Work Item Field Explorer tool.

Work item field explorer

For a description of each attribute, see this post: Work Item Field Attributes - What You Can and Can't Change.

To access the Work Item Field Explorer, you must install the Process Editor (requires that you have installed a version of Visual Studio):

You can list the attributes of fields using the witadmin listfields command.

VSTS and the Inheritance process model

To add fields to a process, modify select field attributes, and review fields added to a process, see Customize a process.

Also, you can view the list of fields defined for a process and the WITs which reference them.


You can change the field name, the index, and the report attributes for any field except system fields by using the witadmin command-line tool. For more information, see Manage work item fields-witadmin.