Overview |  | Roles |  | Work Items |  | Views |  | CMMI |  | Index |  | Glossary |

Project Portal
| Change Request
### Work Item Database
Overview |
States and Transitions |
Fields |
### Process Guidance |
Activities |
Workstreams |
Change Request Fields A change request work item identifies a proposed change to some part of the product or baseline. Change requests must be created when a change is proposed to any work product that is in the configuration management system. The change request work item is used by the change control board to analyze, accept, and reject proposed changes. If a change request is accepted, it is used to generate tasks to implement the change. After changes are implemented, the change request is eventually closed.
Field | Description
--- | ---
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.
Area Path | Used to group the change request into an appropriate feature or team area. The area must be a valid node in the project hierarchy.
Iteration Path | The scheduled iteration in which the change request is carried out.
Assigned To | The current person to which the change request is assigned.
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 1, 2, and 3.
Description | Details about the change request describing what exactly needs to be done.
Attachments | Contains the files that have been attached to the change request to provide additional information such as notes.
Estimate | The estimate 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.
Integrated In | 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.
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. This field appears on the Analysis tab.
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. This field appears on the Analysis tab.
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. This field appears on the Analysis tab. It appears as Impact on Development in the query field.
Impact on Tech Pubs | Describes what impact the change will have on product documentation. This field should include detail about which sections of documentation are affected and what the cost will be to change them. This field appears on the Analysis tab.
Impact on User Experience | Describes what impact the change will have on user experience. This field should include detail about which sections of documentation are affected and what the cost will be to change them. This field appears on the Analysis tab.
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.
Triage | This field is used during the Proposed state. It provides sub-states for a change request awaiting a triage decision. Valid values are Pending (default), More Info, Info Received, Triaged.
Blocked | Indicates if progress on resolving the change request has been blocked. If an Issue work item has been opened to track the blocking problem, a link should be made to that work item as well.
Remaining Work | An estimate in person hours of the work remaining to implement the change. This information appears on the Details tab.
Completed Work | An estimate in person hours of the time spent to date to implement the change. This information appears on the Details tab.
Links | This field shows the other work items that have been linked to the change request. A change request should be linked to the bug work item it was created from, and any tasks created to implement the change.
Resolved By | Identifies who resolved the change request. This information appears in the History field and not in its own field.
Resolved Date | Identifies when the change request was resolved. This information appears in the History field and not in its own field.
© 2005 Microsoft Corporation. All rights reserved. MSF for CMMI Process Improvement: 1.00.0000.00 |