Versions Compared

Old Version 30

changes.mady.by.user Igor Shakhbazyan

Saved on

compared with

New Version 31

changes.mady.by.user Igor Shakhbazyan

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Open the change request you want to work on;
  2. Scroll down the page, then open the Related Records tab;
  3. You can create these types of relationships:
    1. Incidents Resolved by this Change;
    2. Incidents Caused by this Change;
    4. Problems Caused by this Change;
    5. Related Changes;
    6. Related Request.
  4. To create relationships for the Incidents Resolved by this Change, Incidents Caused by this Change, Problems Caused by this Change, Related Changes, please complete the following steps:
    1. Click a lock icon, then click a magnifier icon;
    2. In the new window appeared, choose a necessary option;
    3. Click the lock icon again and then click Save.
  5. To create relationships for the Related Request, please complete the following steps:
    1. Click a magnifier icon;
    2. In the new window that was appeareda, choose a necessary option;
    3. Click Save.

...

Info

The relationship types Incidents Resolved by this Change and 

To use this feature, please complete the following steps (for the Incidents Resolved):

  1. Open the change request you want to work on;
  2. Scroll down the page, then open the Related Records tab;
  3. Click the lock icon near Incidents Resolved by this Change;
  4. In the window appeared, choose incidents that will be resolved by this change request. You can select over one incident;
  5. When you've finished, click the lock icon again;
  6. Then open the Closure Notes tab;
  7. Turn the Complete Originators checkbox on;
  8. After you mark the change request as Completed, all related incidents will be marked Completed as well.

...

When scheduling the change request implementing, it is recommended to avoid time overlaps, to not affect multiple services or CI's at a time. It is a good an excellent practice to follow the rule: "One timeframe - one change request."

...

Change Request Authorization

The change requests that are not standard type must pass authorization procedure (the standard change moves to the Scheduled state automatically, without authorization stage).

The authorization is a request approval by Change Authorities of different levels depending on the risk level.




CABs will be also mentioned here as wellавтоматически переходит в шедулед

осветить механизм

апрувал тикеты

...

OptionDescription
Implemented

This state displays that the change request was fully implemented.

Partially ImplementedThis state displays that the change request was implemented with some exclusions that do not affect the critical functionality of the service.
Not ImplementedThis state displays that the change request was not implemented.
CancelledThis state displays that the change request was cancelled because of authorization failed or cancelled revoked by the caller.
BackoutThis state displays that the change request implementation was not successful, and the previous state of service (or CI) was restored.

...