Versions Compared

Key

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

Creating Change Tasks


If solving change requests requires the participation of several departments, then you can create a change task for each of them. 

To create a change task, please complete the following steps:

  1. Navigate to Change EnablementAll Change Requests and open the change request you need to work on.
  2. Open the Change Task tab in the Related Lists area.
  3. Fill in the form.
  4. Specify start and end dates in the Schedule tab for task implementation.
  5. Click Save or Save and Exit.
FieldMandatoryDescription
NumberYThis field contains a change request task number in CHTXXXXXXX format. It is populated automatically.
ParentYThis field is populated automatically with the number of the parent change request.
Assignment GroupY

Choose a responsible group you wish to assign the task to.

Note

When a change request task is assigned to a responsible group, the Assigned User field becomes non-mandatory. 

There is a dependence between Assigned User and Assignment Group fields. Refer to the Task Auto Assignment article to learn more.

Assigned UserY

Choose a responsible person you wish to assign the task to.

Note

When a change request task is assigned to a responsible person, the Assignment Group field becomes non-mandatory. 

There is a dependence between Assigned User and Assignment Group fields. Refer to the Task Auto Assignment article to learn more.

SubjectYSpecify the task subject.
DescriptionNDescribe the task by giving more details.
PhaseYSpecify the change phase, depending on its schedule.
TypeN

Define the type of change task.Available options:

  • Planning
  • Review
  • Testing
  • Implementation.

Task type can be customized based on business needs (for example, Deployment Task, Code Review Task, Documentation Task).

State Y

Specify the task state. Available choice options:

  • Waiting for change authorization
  • Registered
  • In Progress
  • Completed
  • Cancelled
  • Closed. 
Info
  • The Waiting for change authorization state is displayed when the related change request is in the Registered state and waiting for the CAB approval. Once the change request is authorized, the task state changes to Registered.
  • If the task is moved to the Cancelled state, the user responsible for the parent change request receives an email notification about it.
  • The Closed state appears only when the change task is in the Completed state.


On HoldNSelect the checkbox to show that work on the task is paused. 
Plan is readyN

Select this checkbox to notify the user responsible for the parent change request that the change task plan is ready.
This checkbox is active only for change tasks in the Registered state.

When all change tasks related to the parent change request are saved with this checkbox selected, the user responsible for the parent change request receives an email notification that all of the change task plans are ready, and the authorization is required.

Followers ListNThis is a list of users who subscribed to receive notifications about this change task by clicking the Follow button. This field is read-only. 
Schedule tab
Planned Start DatetimeNThe date when the assigned person is supposed to start working on this task.
Planned End DatetimeNThe date when the task should be in the Completed or Closed state.
Previous TaskNThe task that was done before.
Actual Start DatetimeNThe date when the assigned person started to work on this task. The agent should fill in this field.
Actual End DatetimeNThe date when the assigned person finished the work on this task. The agent should fill in this field.
Next TaskNThe task that will be done after. 


Info

You can create as many change tasks as you need.


Change Task State Model


Image Added


Creating a Change Request Announcement


Create an announcement informing related to the change request process.

To create a Change Request announcement, please perform the following steps:

  1. Navigate to Change Enablement → All Change Requests and open a change request you need to work on.
  2. Click the Create Announcement button in the change request form.
  3. Fill in the fields. 
  4. Click Save or Save and Exit.

Image Added

Field

Mandatory

Description

Number 

YThis field is populated automatically with the announcement number in ANCMXXXXXXX format.
StateY

This field is populated automatically with New.

Related ChangeYThis field is populated automatically with the identifier number and change request subject.
Announcement Type Y

Available options:

  • Maintenance – this type of announcement informs that some service or CI recovery activities are going to be under maintenance in the specified period;
  • Urgent Maintenancethis type of announcement informs that some service or CI recovery activities will be under maintenance at the nearest time due to high urgency. 
ServiceYSelect the service affected by the change request.
Recipient EmailNSpecify the email of the announcement recipient. You can add more than one email, separated by commas.
Reviewer's EmailNSpecify the email of the announcement reviewer. You can add more than one email, separated by commas.
via EmailNSelect the checkbox to send this announcement via email. It will be sent to all addresses specified in the Recipient Email field.
via PortalNSelect the checkbox to display this announcement on the Service Portal in the Portal Announcements area.
SubjectYThis field will be populated automatically with the change request subject.
Announcement BodyNType the message you need to share with users about this incident. You can design the announcement body using the built-in editor functionality, such as formatting, working with tables and media, lists, styles, and headings.
SignatureNReference to the Announcement Signature.
DescriptionNDescribe the announcement.

Creating Relationships


You can create relationships between changes and other types of tasks.

Relationship Types

Type

Description

Caused by IncidentsThis change request is the cause of the incidents specified.
Caused by ProblemsThis change request is the cause of the problems specified.
Caused by RequestsThis change request is the cause of the service requests specified.
Related ArticlesThis change request is related to the Knowledge Base Articles specified.
Related User QueryThis change request is related to the user query specified.
Related IncidentsThis change request is related to the incident specified.
Related ProblemsThis change request is related to the problem specified.
Resolved IncidentsThe incidents specified will be resolved after resolving this change request.

Resolved Problems

The problems specified will be resolved after resolving this change request. 


Note

Only assigned users with the itsm_agent role can edit the fields in the Related Records tab in any change request state except Closed.

To add a new relationship, please complete the following steps:

  1. Navigate to Change Enablement → All Change Requests and open the change request you want to work on.
  2. Open the Related Records tab.
  3. Click the magnifier icon Image Addednext to the appropriate field.
  4. In the window appeared, choose a necessary option.
  5. Click Save to apply changes

This picture illustrates state models of the change requests of three different types:

  1. Standard Change;
  2. Normal Change;
  3. Emergency Change.

Also, you can find a brief description of every state under the picture.

Image Removed

States Description

Registered

This state is for the newly created change requests. If this is a Standard change, then it transitions straight to the In Progress state, as the Standard is a pre-approved type. If this is a Normal or Emergency change request, then the request transitions to the Authorization state.

Authorization

This state is mandatory for Normal or Emergency Changes. In this state, the request must be reviewed and authorized by the responsible persons or groups (see more on the Change Request Authorization). After all authorization steps have been passed, the change request transitions to the Scheduled state.

Scheduled

In this state, the change request has the following prerequisites:

  1. Planned start date;
  2. Planned end date.

So it is preliminary known when the change will be implemented.

In Progress

This state displays that the request is in progress of implementation now. When the work is over, the state has to be changed to the Completed.

Note

When Assigned User changes to another person, the Change state changes from the In Progress to Registered value.

Completed

After the work is over and the request is transited into this state, the requester can perform the tests and give feedback by the results of the implementing. After this, change the state to the Closed

Post-Implementation Review

When the request is completed (whether successfully or not), the Change Advisory Board has a right to perform Post-Implementation Review on the basis of the implementing. It is a good practice that allows gaining the "lessons learned" after the implementation, especially if there were any issues on the way.

For this, the change request state must be changed to the Post-Implementation Review state from the Completed state. After the review, similarly to the Completed state, mark it as Closed.

Closed

All activities on this change request are over, and it cannot be reopened
  1. .


Table of Contents
absoluteUrltrue
classfixedPosition