---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://www.servicenow.com/docs/r/it-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Create a change task

# Create a change task {#ariaid-title1}

* Release version: Australia
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 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  
Note:  
If the change task form is read-only, confirm that you have a required role and that the change request is in an editable state. Editing is not available in certain states, such as Closed. For
state-based restrictions, see [Legacy: State model and transitions](https://www.servicenow.com/docs/eEnXKkuIAPsBuC6J~pHW6A "Change Management offers a state model to move and track change requests through several states.").

## 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 AllChangeOpen.
2. Select the change request to add a change task.
3. In the Related Links section, select Change Tasks tab and then, select New.  
   If the New button does not appear, confirm that you have the required roles and that the change request is in a state that allows adding change tasks. Adding change tasks can be restricted by change state. For more information on state restrictions, see [Legacy: State model and transitions](https://www.servicenow.com/docs/eEnXKkuIAPsBuC6J~pHW6A "Change Management offers a state model to move and track change requests through several states.").
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](https://www.servicenow.com/docs/A_SlHzQ42OQzfVAdriHVrQ "You can copy details of an active or canceled change request to a new change request.")
5. Fill in the fields, as appropriate.  
   {#create-a-change-task__table_blp_xnl_sy__entry__2}

   | 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. |
   | Number of copies | The number of change tasks to generate for each scheduled date. Note: This field appears only when you choose Multiple Dates option. |
   | Change Task Types | Tasks that are implemented for each phase of work they represent: * Planning: Tasks that plan and prepare the change before implementation. * Implementation: Tasks that carry out the change. The Planned start date and Planned end date values must fall within the planned dates of the change request. * Testing: Tasks that verify the change works as expected. * Review: Tasks for post-implementation 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. {#create-a-change-task__ul_r3q_hwc_gz} |
   | 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. |
   [Table 1. Change Task form]

   {#create-a-change-task__table_blp_xnl_sy}
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.
**Related concepts**   

* [Unauthorized change request](https://www.servicenow.com/docs/6mf8zPEdSPvf7_x9hnJlxg "Understand how an unauthorized change activity on a configuration item (CI) is captured and managed, so that you can review and take timely action on this change.")  
**Related tasks**   

* [Create a change request from a configuration item (CI)](https://www.servicenow.com/docs/7qZPeQ9Z1C~1dqJGs6d21A "Create a change request from a list of configuration items (CIs), or add selected CIs from a list to a change record.")
* [Create a standard change request from the catalog](https://www.servicenow.com/docs/lFBX77OyLsEgiKdwxZ8aBQ "You can create a standard change request from the published standard change catalog templates.")
* [Copy a change request](https://www.servicenow.com/docs/A_SlHzQ42OQzfVAdriHVrQ "You can copy details of an active or canceled change request to a new change request.")

*[\>]: and then