Title

Required. The title provides a concise overview of the task to be completed. The title should be descriptive enough to allow the team to understand what area of the product is affected and how it is affected.

Type

Indicates whether the task is a development task, test task, analysis task, user experience task (Ux), or user experience task (Ue). Setting the type field determines the meaning about the state of the work when the task is closed. It also helps when querying for tasks assigned to certain areas, such as finding all test related tasks. Valid values are Analysis, Ux, Ue, Development, or Test.

Affected Area

Used to group the task into an appropriate feature or team area. The area must be a valid node in the project hierarchy.

Planned Iteration

The scheduled iteration in which the task is carried out.

Assigned To

The current person that the task is assigned to.

State

Required. A task can be in the Proposed, Active, Resolved, or Closed states.

Reason

Required. The reason a task is in the current state.  For example, the task may be closed because it is Deferred.

Priority

Required. The priority field is a subjective importance rating used to determine which tasks to complete first. Valid values are Expedite, High, Medium, and Low.

Description

Details about the task describing what exactly needs to be done.

File Attachments

Links to files or other work items. In the case of a development or test task, the supporting scenario or quality of service requirement should be attached. It also contains any attachments such as notes on the task.

Estimate

The amount of work in person hours that remain to finish the task. Ideally this amount should not exceed 120 hours; such tasks should be divided into smaller tasks.

ID

The unique identifier used to identify the task. Team Foundation Server automatically creates the ID when the work item is created.

Changesets

Identifies the changesets which introduced the work resulting from completing the task. This field only applies to development tasks.

In Build

Identifies the build number in which the task is implemented. This build number is used so that testing can verify the task if testing is required.

History

Describes what activity has occurred each time the task is updated with new information. This field is a running history of activity on the task.

Requires Review

Indicates if the task requires a review to verify that it is completed correctly. This field is a value of Yes or No.

Requires Test

Indicates if the task requires a test to verify that it is completed correctly. This field is a value of Yes or No.

Created By

Identifies who created the task.

Created Date

Identifies when the task was created.

Changed By

Identifies the person who last made a change to the task.

Changed Date

Identifies the date the task was last changed.

Closed By

Identifies the person who closed the task.

Closed Date

Identifies the date the task was closed.