Reportable Fields Reference for Visual Studio ALM
A default set of fields appears in the relational warehouse database or the cube. The following tables list those reportable fields defined in the default process templates provided with the current release of Team Foundation Server. These fields have a reportable attribute value of Detail, Dimension, or Measure. See Add and Modify Work Item Fields to Support Reporting.
For a complete list of fields that are defined in the default process templates, see Work Item Field Reference for Visual Studio ALM. If you upgraded a team project, you may need to perform additional tasks before you can work with some of these fields. For more information, see Configure features after a TFS upgrade.
Detail fields are written to the relational warehouse database, but not to the cube.
A number that represents the relative priority for a bug, product backlog item, or task. (Scrum process template only.)
The date and time stamp when a test case or shared step is revised.
Dimension fields are written both to the relational warehouse database and to the cube.
The name of the person who responded to the code review.
The date and time when the person responded to the code review.
The name of the team member who activated or reactivated the work item.
The date and time when the work item was activated or reactivated.
The type of activity that is required to perform a task.
Groups the work items into product feature or team areas. The area must be a valid node in the project hierarchy.
The name of the team member who currently owns the work item.
The status of a test case. You can specify the following values:
Indicates that progress toward resolving a bug, change request, requirement, or risk is suspended. Allowed values are Yes and No. (CMMI process template only)
The name of the team member who modified the work item most recently.
The date and time when the work item was modified.
The name of the person who closed a work item.
The date and time when a work item was closed.
The status selected by the reviewer when closing the code review request. The number is stored in the system and written to the data warehouse as follows:
The name of the team member who created the work item.
The date and time when a work item was created.
The forecasted due date by which an issue will be resolved. (Agile process template only)
The date and time when the schedule indicates that the task will be completed.
The product build number, also known as a revision, in which a bug was found.
The unique identifier that is assigned to a work item. Work item IDs are unique across all team projects and work items that are defined in a team project collection.
The product build number that incorporates the code or fixes a bug.
Indicates that the shared step is associated with an expected result. Allowed values are Yes and No.
Groups the work items by named sprints or time periods. The iteration must be a valid node in the project hierarchy.
A subjective rating of the bug, issue, task, or test case as it relates to the business. You can specify the following values:
The number of stars that an item receives from a reviewer in a star-based ranking system. (Feedback Response)
The number is stored in the system and written to the data warehouse as follows:
The reason that the work item is in the current state. Values are specific to both the state and the type of work item. The field is not tracked for test cases or shared steps.
The name of the team member who resolved the bug or user story.
The date and time when the bug or user story was resolved.
The reason that the bug was resolved (for example, it was fixed).
A number that is assigned to the historical revision of a work item.
A subjective rating of the relative uncertainty about the successful completion of the user story. You can specify the following values:
A subjective rating of the effect of a bug, issue, or risk on the project. You can specify the following values:
A subjective rating of the user story, task, issue, or bug compared to other work items of the same type. An item that is assigned a lower number should be fixed before an item that is assigned a higher number.
The date and time when the schedule indicates that the task will start.
The current state of the work item. The valid values for state are specific to each type of work item.
The team project to which this work item belongs.
A short description that summarizes what the work item is and helps users to distinguish it from other work items in a list.
Work Item Type
The name of the work item type.
Measure fields are written to the data warehouse and contain pre-calculated sum values.
A subjective unit of measure that captures the relative business value of a product backlog item compared to other items of the same type. An item that is assigned a higher number should be considered as having more business value than an item that is assigned a lower number. (Scrum process template only)
A measure of the amount of work spent on a task.
The relative rating for the amount of work that a product backlog item will require to implement. (Scrum process template only)
A measure of the amount of work that is required to complete a task.
A measure of the amount of work that remains to finish a task.
The relative rating for the amount of work that a requirement will require to implement. (CMMI process template only)
A subjective unit of measure that captures the size of a user story. If you assign more points to a user story, you indicate that more work is required to implement it. (Agile process template only)