Create a change request - Product Documentation: Washington DC

Create a change request

IT Service Management > Change Management >

Create a change request

Create a change request to implement a controlled process for modifying approved and supported configuration items (CIs).

Role required: itil, admin, or sn_change_write

A change request records the detailed information about the change, such as the reason of the change, the priority, the risk, the type of change, and the change category.

If you use conflict detection, the planned start and end dates and the configuration item (CI) are required.

Create the change request with one of these options. Option Description From the Change module You can create all three types of change from the Change module. Navigate to All > Change > Create New . Select Normal , Emergency , or Standard changes.

If you are an upgrade customer and willing to use change models, you must enable the change model properties. For information on change models and its properties, see Change models .

When you enable the change model properties, you see the following tabs when you navigate to All > Change > Create New .

Models : Shows all the available models available to select. Preapproved : List of preapproved models to select. Pinned : Models that you have pinned from the Models and Preapproved tabs. All : All models are available to select.

From an incident or a problem As a user with the sn_change_write role, you can create a standard, normal, or an emergency change from an incident or a problem. Open the incident or problem. Right-click the form header and select Create Normal Change , Create Standard Change , or Create Emergency Change .

From an existing change record If the administrator enabled the change request copy option, you can create a new change by copying an existing change record. Open the change record that you want to copy. Click Copy Change .

Note: If the create task workflow sets the create_from field in the [change_task] table to workflow , manually created tasks from the existing change record are copied.

On the form, fill in the fields. Table 1. Change Request form Field Definition Number Change request number. Requested by User who requested the change. This field is available in the Change Requests list view, so that you can see who requested a particular change. Category Category of the change, for example, Hardware , Network , Software . Service Business service that you want to make available for the change request. Note: If you select a business service as the configuration item and that business service is also listed as the configuration item in any other active task, the active tasks icon ( ) appears. Click this icon to view the list of all the other active tasks that are affecting the business service. You can view the BSM map (dependency view) of the selected business service by clicking the dependency icon ( ). Service Offerings Consists of one or more service commitments that uniquely define the level of service in terms of availability, scope, pricing, and packaging options. You can choose to receive different levels of performance and features for a given service through service offerings. You must select a service to filter the available service offerings. Configuration item Select Add to add a CI for the change. You can add a CI for a change in New state only.

CI that the change applies to. Change requests can be associated with any type of CI, including service offerings, providing detailed access to SLA and availability requirements. When you select a dynamic CI group, all the configuration items related to the selected dynamic group will be populated in the Affected CIs related list. In the Affected CIs related list, you can also manually add and delete the dynamic CI groups. When you add a dynamic CI group, all the related CIs are added, and when you remove a dynamic CI group, the related CIs are removed.

After selecting a CI, you can click the health dashboard icon ( ) to view the CI health details.

Note: By default, Service Offering is filtered out and CIs with Principal Class are selected. The Principal Class filter functionality is applicable to new customers starting the Paris release.

See Refresh impacted services properties

Priority Priority is based on impact and urgency, and it identifies how quickly the service desk should address the task. Risk Risk level for the change. The risk of a change can be defined manually as High , Moderate , or Low . You can also use Risk Calculation and Risk Assessment to drive the risk value of the change.

Impact Impact is a measure of the effect of an incident, problem, or change on business processes. Type Type of change request. This field is read-only. State State of the change request. The default state is New. Conflict status Status that indicates whether there is a conflict for this change or the conflict is not run. Conflict last run Date and the time when the conflict was last run. Assignment group Group who will work on the change request. The business rule Populate Assignment Group based on CI/SO populates the Assignment group field available for the CI or the service offering consecutively. Note: The business rule is triggered when a change request is created or updated and when the Assignment group and the Assigned to fields are empty. If you want to override the default value, you need to create new properties and provide the field in the property value that must be used to populate the Assignment group field. Create the properties in the following order of preference: com.snc.change_request.ci_assignment_group.field_name : Identifies which CI field populates the Assignment group field. com.snc.change_request.service_offering_assignment_group.field_name : Identifies which service offering field populates the Assignment group field. Assigned to User that the change is assigned to. If an assignment rule applies, the change is automatically assigned to the appropriate user or group. Short description Summary of the change. Description Detailed description of the change.

To plan the change, click the Planning tab and enter information. This information is critical for change approvers. Click the Schedule tab. Enter as much information about the scheduled dates as you have. Some of the fields are available for normal or emergency changes only because standard changes are preapproved. Note: For normal or emergency changes, enter the planned start and end dates and actual start and end dates manually. Populate the actual start and end date fields during the Implement state as the assignee begins and completes the work.

If the form is configured to show the CAB required check box, select it to indicate that CAB approval is required before implementation. The CAB date field in the change request is automatically updated with the date in the Meeting start time field of the CAB meeting form. If there is an unplanned CI activity, select the Unauthorized check box to determine if the change is an unauthorized change. For more information, see Unauthorized change request .

Note: This check box is available only for emergency change requests.

If the form is configured to show the CAB delegate field, select the user who attends the CAB meeting to describe the change. In the CAB recommendation field, enter notes or recommendations related for the CAB meeting.

Click the Conflicts tab. To detect change conflicts, click Check conflicts . Right-click the form header and click Save. Review entries in the related lists and modify the entries as appropriate. Table 2. Default Change Request related lists Field Description Affected CIs List of CIs (from the CMDB ) affected by the change. You can associate multiple affected CIs with a change. Impacted services/CIs List of CIs, such as business services or from other CI classes, that are impacted by the affected CI in the change. You can associate multiple impacted CIs with a change. Service Offerings List of service offerings affected by the change. You can associate multiple service offerings with a change. This related list is available only when a service offering is selected. If there are service offerings associated to the Impacted Services, then refresh the Impacted services/CIs related list to view the offerings.

Note: If you have customized the default view of your form or related list prior to the Paris release, you cannot see the field or the related list by default. Modify the form to add them manually. Approvers This list is automatically generated from the workflow. You can also view the Group of approvers assigned to the task. Change Tasks The list of tasks can be created from a workflow. The default workflow generates tasks in the Implementation state. You can also create a new change task. The Planned start date and Planned end date in task type Implementation must fall within the planned start and end dates specified in the change request. Problems If the change was generated from a problem, this list is generated automatically. Incidents Fixed by Change List of incidents that require the change for resolution. Incidents Caused by Change List of incidents caused by the implementation of the change. CAB Agenda Items List of agenda items and details of respective items. For example, the meeting start and end time, allocated time for the meeting, state of the meeting, and the decision made for that agenda item. Note: The CAB Agenda Items related list is not shown on the form when the list is empty. This feature is available only for Jakarta instances.

When the change request is ready to move to the next state, click Request Approval . The state is moved forward based on the type of change request: Assess state: Group level approval for a normal change request. Approval records are automatically generated based on the Assignment group . You can conduct peer and technical reviews of the proposed change. Authorize state: An emergency change request. Scheduled state: Pre-approved standard changes.

Note: To mail the change record, click the more options icon ( ) in the content frame and select Email . Both the user who requested the change and the user who is assigned to the change are automatically populated in the list of recipients. To view the calendar, click View Calendar in the title bar of the Change Request form.

Process a change request

Create a change request from a configuration item (CI) Create a change request from a list of configuration items (CIs), or add selected CIs from a list to a change record. Create a standard change request from the catalog You can create a standard change request from the published standard change catalog templates. Copy a change request You can copy details of an active or canceled change request to a new change request. Create a change task You can create change tasks for a change request. A change task is a piece of work related to the change request. For example, there can be tasks to plan the change, implement the change, and test, and review the work. Unauthorized change request Understand how an unauthorized change activity on a configuration item (CI) is captured and managed, so that you can review and take timely action on this change.

Parent Topic: Using Change Management

Related concepts State model and transitions Conflict calendar

Related tasks Place a change request on hold