Create a change task

  • Release version: Yokohama
  • Updated January 30, 2025
  • 3 minutes to read

    • 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.

    Before you begin

    Before creating a change task, confirm you have the required roles. If not, contact your administrator to request access.

    Role required: itil, admin, or sn_change_write

    About this task

    Change tasks can be created manually or from a workflow. The Change Tasks related list is displayed by default and includes all manual and workflow-generated change tasks.

    To edit existing tasks or create tasks, from the Related Links section, select the Change Tasks tab and then select New.

    If the Change task related list is not visible, scroll down the change form or verify that your role has permission to view it. If the list is still not visible, contact your IT administrator to verify your permissions and form configuration.

    Procedure

    1. Navigate to All > Change > Open.
    2. Select the change request to add a change task.
    3. In the Related Links section, select Change Tasks tab and then, select New.
    4. To associate an existing change task with the change request, open the change task record and update the Change field to the target change request and save the record.
      Note:
      The New button creates a change task and doesn't attach an existing change task. To carry tasks to the new change request, Copy a change request
    5. Fill in the fields, as appropriate.
      Table 1. Change Task form
      Name Definition
      Configuration item The configuration item (CI) or service that the change task applies to.
      Planned start date The date you plan to begin working on the task.
      Planned end date The date the change task is planned to be completed.

      If the task type is Implementation, the Planned start date and Planned end date values must fall within the planned start and end dates specified in the change request.
      Type The type of change task, Planning, Implementation, Testing, or Review. The default workflow generates tasks in type Planning.
      State The state of the change task:
      • Pending: Not yet ready to be worked on. Waiting for a predecessor task to complete or for the scheduled start time.
      • Open: Ready to be worked but not yet started.
      • In progress: Actively being worked on.
      • Closed: Inactive and closed. Set the Close code and Close notes fields before you move the task to Closed.
      • Canceled: No longer required. The task is closed without being completed.
      On hold The On hold check box indicates whether the change task is on hold. Provide an On hold reason if a change task is placed on hold.
      Assignment group The group that the change task is assigned to.
      Assigned to The user that the change task is assigned to. If an assignment rule applies, the change task is automatically assigned to the appropriate user or group.
      Short description A summary of the task.
      Description A detailed description of the task.
    6. To enter work notes for the change task, select the Notes tab.
    7. To record the reasons for closing a task, select the Closure Information tab and set the Close code and Close notes fields.

      Each change task is closed individually. The Close code applies to the current change task and not to other change tasks on the change request.

      Important:

      Close codes and close notes apply to individual change tasks only and do not affect other change tasks on the change request. Once you submit or close a change task, you cannot revert it to an earlier state, such as Open or In Progress.

    8. Select Submit.
      The change task is added to the change request. The assigned user receives a notification that a task was assigned to them.