Role required: change_manager.
Create a change request
To create a change request, complete the following steps:
- Navigate to Change Enablement → New.
- Fill in the form.
- Click Save or Save and Exit to apply the changes.
You can copy the record number, title and link via the hamburger menu. To do so, click Generate link.
New Change Request form fields
General tab
| Field | Mandatory | Description |
|---|---|---|
| Number | Y | This field is populated automatically and contains a change request number in CHGXXXXXXX format. |
| Caller | Y | The request originator. |
| Company | N | A company to which the request is related. |
| Change Type | Y | Specify the change type. Available choice options:
Based on the selected option, the request should be authorized differently. Refer to the Change Request Authorization article to learn more. |
| Service | Y | The service affected by this change request. |
| Related CIs | N | Service-related CI that will be affected by this change request. |
| Copy CIs to Originators | N | Select this checkbox to automatically relate configuration items from the problem to problem originator entities. |
| Assignment Group | Y | Specify a responsible group to work on the request. When a change request is assigned to a responsible group, the Assigned User field becomes non-mandatory. The same goes for other task objects, like incidents or service requests. There is a dependency between the Assigned User and Assignment Group fields. Refer to the Task Auto Assignment article to learn more. |
| Assigned User | Y | Specify a responsible person to work on the request. When a change request is assigned to a responsible user, the Assignment Group field becomes non-mandatory. The same goes for other task objects, like incidents or service requests. There is a dependency between the Assigned User and Assignment Group fields. Refer to the Task Auto Assignment article to learn more. |
| Subject | N | Describe the request briefly. After saving, the field is hidden on the form. |
| Reason | Y | Justify the request. |
| Followers List | N | The list of users who follow the request for tracking the updates. The field appears if at least one user followed the problem. It is read-only. |
| State | N | Specify the work state and progress. This field is populated automatically with the Registered state. Other states you can find in State Models. |
| Impact | Y | Measure the effect that a change request may cause on the business processes and select one of the available choice options:
|
| Urgency | Y | Identify how soon a change request will have an impact on the business and select one of the available choice options:
|
| Probability | Y | The level of possibility of disruptive or harmful event occurrence. Possible choice options:
|
| Priority | Y | Priority is a function of impact and urgency. It identifies the importance of a request. Available choice options:
|
| Risk | Y | Risk is a function of impact and probability. It is a possible event that could cause loss or harm. Available choice options:
|
| Change Authority | Y | The person or group responsible for authorizing the request. This field is populated automatically based on the value in the Change type field. |
| Customize CAB | See Processing Change Requests. |
Schedule tab
| Field | Mandatory | Description |
|---|---|---|
| Planned Start Datetime | N | Pick a date and time to start the request processing. Fill in this field before a change request can be processed. |
| Planned End Datetime | N | Pick a date and time to finish the request processing. Fill in this field before a change request can be processed. If a request is not processed during the planned period, it is canceled. |
| Planned Downtime | N | If a service downtime is expected, specify its duration here. The responsible person must fill in this field before a change request can be processed. |
| Downtime Notes | N | Add any notes about the planned service downtime here. Fill in this field before a change request can be processed. |
| Possible Conflicting Changes | N | Change requests that have a time overlap with this request. It possibly can impact request implementation. This field is populated automatically. |
| Actual Start Datetime | N | Pick a date and time for the actual start of the request processing. |
| Actual End Datetime | N | Pick a date and time for the actual finish of the request processing. |
| Actual Downtime | N | If the service downtime occurs, specify its duration here. The field is mandatory if the Planned Downtime field was filled in, and the state of the change request is Completed. |
Planning tab
| Field | Mandatory | Description |
|---|---|---|
| Preparation | Y | This plan specifies the steps that need to be done and the criteria to be met before implementing the change. Fill in this field before a change request can be processed. |
| Core Activities | Y | Describe the process of change implementation. Fill in this field before a change request can be processed. |
| Validation | Y | The process of how the change must be tested after the implementation. Fill in this field before a change request can be processed. |
| Backout | Y | The plan specifies the processes that will roll back the system, service, or CI condition to its previous state in case of a failed implementation. Fill in this field before a change request can be processed. |
Closure Information tab appears when the change request state is Completed.
| Field | Mandatory | Description |
|---|---|---|
| Complete originators | N | Select this checkbox to make the originators related to this request be completed along with it. |
| Closure Notes | Y | Specify some notes summarizing the implementation process. |
| Closure Code | Y | Specify a closure code. For more information, refer to the Closure Code article. |
When a change request is Scheduled, In Progress, or Completed, fields on the record form become read-only, excluding the following:
- Assignment Group
- Assigned User
- State
- Followers List
- Additional Comments on the Notes tab
- Actual Downtime on the Schedule tab
- All fields on the Related Records tab
Change Request Prioritization
The priority of the change request can be figured out based on its impact and urgency using a priority matrix.
The impact of a change indicates the potential damage in case of emergency changes or effect in case of standard or normal changes. The damage will be done to the business user, service, or CI.
In SimpleOne, the impact can be categorized as:
- Low
- Medium
- High
- Very High
The urgency of a change indicates the measure of time in the following cases:
- Until a change impacts the business – in case of emergency changes.
- Until lack of change implementation will impact the business services or CI – in case of standard or normal changes.
In SimpleOne, the urgency can be categorized as:
- Low
- Medium
- High
- Very High
Based on the priority, the changes can be categorized as:
- Low
- Moderate
- High
- Critical
Impact / Urgency Low Medium High Very High Low Low Low Moderate High Medium Low Moderate Moderate High High Moderate Moderate High Critical Very High High High Critical Critical
Risk Management
The risk of the change request can be figured out based on the following metrics:
- Impact
- Probability
- IT Service Business Criticality
The IT Service Business Criticality metric specifies how crucial the disruption of this service for the business can be. The options are High or Low.
Risk metrics for IT Service Business Criticality = Low
| Probability / Impact | Low | Medium | High | Very High |
|---|---|---|---|---|
| Low | Low | Low | Medium | High |
| High | Medium | Medium | High | High |
Risk metrics for IT Service Business Criticality = High
| Probability / Impact | Low | Medium | High | Very High |
|---|---|---|---|---|
| Low | Low | Medium | High | High |
| High | High | High | High | Very High |
Create a change request
You can create change requests based on two specific issue types:
- Problem
- Incident
When you have fixed an incident or a problem, and, as a result, you have found a need in a change, you can create change requests straight out of incidents or problems.
You can create a change request out of problems and incidents in any State.
out of problem
To create a change request out of a problem, complete the following steps:
- Navigate to Problem Management → All Problems and open the problem you need to work on.
- In the hamburger menu
, select Create Change. - Choose the type of change you need to create:
- Standard Change
- Normal Change
- Emergency Change
- Fill in the fields of the change request.
- Click Save or Save and Exit.
As a result, a new change request is created in the Registered state. There is a reference to the problem in the Caused by Problems field of the Related Records tab.
out of incident
To create a change out of an incident, complete the following steps:
- Navigate to Incident Management → All Incidents and open the incident you need to work on.
- In the hamburger menu , select Create Change.
- Choose the type of change you need to create:
- Standard Change
- Normal Change
- Emergency Change
- Fill in the fields of the change request.
- Click Save or Save and Exit.
As a result, a new change request is created in the Registered state. There is a reference to the problem in the Caused by Incidents field of the Related Records tab.
