Initiating and Classifying a Change Request
Updated: May 13, 2016
Applies To: System Center 2012 SP1 - Service Manager, System Center 2012 R2 Service Manager, System Center 2012 - Service Manager
The procedures in this section describe how to initiate and classify a change request in System Center 2012 – Service Manager from start to finish.
For a detailed description of the complete scenario for initiating and classifying a change request, see Sample Scenario: Managing Changes and Activities.
A change request normally results in a change to a configuration item. Therefore, it is important to understand the difference between a related item and a linked or affected item. A related item indicates that an association exists between the change request and a configuration item or other change requests. In other words, the change request might affect the related item or it might not. An affected or linked item indicates that the change request is tied directly to the item and that the change will affect the item itself.
Complete the following steps to initiate and classify a change request.
| Task | Description |
|---|---|
| Step 1: How to Create a New Change Request | Describes how to create a new change request for a service to modify server infrastructure. |
| Step 2: How to Add Related Items to a Change Request | Describes how to add items, such as files, to a change request. |
| Step 3: How to Add Manual Activities to a Change Request | Describes how to add a manual activity to a change request to manage tasks. |
| Step 4: How to Add Dependent Activities to a Change Request for Release Records | Describes how to add a dependent activity to a change request for a release record. |
See Also
Managing Changes and Activities in System Center 2012 - Service Manager