Title

Required. The title provides a concise overview of the change request 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.

Justification

Describes why the change request is proposed and what value the change brings to the product and customer.

Affected Area

Used to group the change request 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 change request is carried out.

Assigned To

The current person that the change request is assigned to.

State

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

Reason

Required. The reason a change request is in the current state.  For example, the change request may be closed because the change request validation test passed.

Priority

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

Description

Details about the change request describing what exactly needs to be done.

File Attachments

Links to files or other work items. A change request should be linked to the bug work item it was created from, and any tasks created to implement the change. It also contains any attachments such as notes on the change request.

Estimate

The amount of work in person hours that remain to finish the change request.

ID

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

Change Sets

Identifies the change sets which introduced the changes upon completing this change request.

In Build

Identifies the build number in which the change request is implemented. This build number is used so that testing can validate the change request.

History

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

Analysis/Impact on Architecture

Describes what impact the change will have on architecture. This field should include detail about which sections of the architecture are affected and what the cost will be to change them.

Analysis/Impact on Test

Describes what impact the change will have on testing. This field should include detail about which tests are affected and what the cost will be to change them.

Analysis/Impact on Design/Development

Describes what impact the change will have on development and product designs. This field should include detail about which designs are affected and what the cost will be to change them.

Analysis/Impact on UE/Tech Pubs

Describes what impact the change will have on user education and product documentation. This field should include detail about which sections of documentation are affected and what the cost will be to change them.

Created By

Identifies who created the change request.

Created Date

Identifies when the change request was created.

Changed By

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

Changed Date

Identifies the date the change request was last changed.

Closed By

Identifies the person who closed the change request.

Closed Date

Identifies the date the change request was closed.