Title

Required. The title provides a concise overview of the issue to be completed. The title should summarize the cause and situation of the issue and distinguish the issue from other issues.

Affected Area

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

Assigned To

The current person that the issue is assigned to.

State

Required. An issue can be in the Active, Resolved, or Closed states.

Reason

Required. The reason an issue is in the current state.  For example, the issue may be closed because it is Resolution Accepted.

Impact on Project Promise

A subjective rating describing the severity of the issue on impacting the customer expectation. Valid values are Critical, High, Medium, and Low.

Priority

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

Description

Details about the issue describing the cause, event, or situation of the issue, and what work is impacted, or will be impacted.

File Attachments

Links to files or other work items providing more information around the issue. Tasks that will be implemented to take corrective action should be linked to the issue.

Escalate

Indicates if the issue is critical and is affecting the critical path of the project plan. Valid values for this field are Yes or No.

ID

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

Analysis

Describes the root cause and potential solutions for the issue.

Corrective Action Plan

Describes the proposed corrective action that is agreed upon.

Corrective Action Actual Resolution

Describes the actual action taken to correct the issue.

History

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

Target Resolve By

A date of when the issue becomes critical and begins affecting the critical path of the project plan.

Planned Iteration

The scheduled iteration in which the issue is addressed.

Created By

Identifies who created the issue.

Created Date

Identifies when the issue was created.

Changed By

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

Changed Date

Identifies the date the issue was last changed.

Closed By

Identifies the person who closed the issue.

Closed Date

Identifies the date the issue was closed.

Resolved By Date

Identifies the date the issue was resolved.