Role required: change_manager.
To create a change, please complete the following steps:
- Navigate to Change Control → Create New;
- Fill in the form and click Save.
The form description
| Field | Description |
|---|---|
| Number | Change request number. This field should have format CHGXXXXXXX. It is filled automatically. |
| Change type | The change type. Available choice options:
|
| Requested by | The originator of the change request (also known as the caller) |
| Service | The service that will be affected by this change request. |
| Related CIs | Service-related CI that will be affected by this change request. |
| Assigned User | Specify a responsible person to work on the request. When Assigned User changes to another person, the Change state changes from the In Progress to Assigned value. |
| Assigned Group | Specify a responsible group to work on the request. |
| Subject | A brief description of the request. |
| Reason | A justification of the request. |
| Description | A detailed description of the request. |
| State | This field displays the work state and progress. Available choice options:
|
| Change Authority | The person or group who is responsible to authorize the request. |
| Probability | The level of possibility of disruptive or harmful event occurrence. Possible choice options:
|
| Impact | The measure of the effect that a change request may cause on the business processes. Available choice options:
|
| Urgency | The measure of time until a change request has an impact on the business. Available choice options:
|
| Priority | Priority is a function of impact and urgency. It identifies the importance of a request. Available choice options:
|
| Risk | Risk is a function of impact and probability. It's a possible event that could cause loss or harm. Available choice options:
|
| The Schedule Tab | |
| Possible Conflicting Changes | Change requests that have time overlap with this request. It possibly can impact request implementation. |
| Planned Start Date | Pick a date and time you need the request to be started processing. The caller must fill this field. |
| Planned End Date | Pick a date and time you need the request to be finished processing. The caller must fill this field. |
| Planned Downtime | If service downtime is expected, then put down its duration here. |
| Downtime Note | You can put any notes about planned service downtime here. |
| Actual Start | Pick a date and time when the request was started processing. The responsible person must fill this field. |
| Actual End | Pick a date and time when the request was finished processing. The responsible person must fill this field. |
| Actual Downtime | If service downtime took place then put down its duration here. |
| The Planning tab | |
| Pre-test Plan | This plan specifies the steps that need to be done and the criteria to be met before implementing the change. |
| Change Plan | Describe here the process of change implementing. |
| Test Plan | The process of how the change must be tested after implementing, |
| Backout Plan | The plan that specifies the processes rollback the system or service or CI condition to its previous state, in case of a failed implementation. |
