The life cycle of tasks as part of a change

Tasks, similar to change requests, go through many status transitions as they progress. The status in which a task is generated, depends on the status of the parent change request.

The following example shows the flow changes, approval, task groups, and tasks that are available with the out-of-the-box configuration.

1. A change request starts in the Draft status. Any related task groups or tasks are in Staged status.
   • If a change request is canceled, all the task groups and tasks associated with the change are also canceled.
   • If a task group is canceled, all child tasks of that task group are also canceled.
2. The change request moves into the Request For Authorization status and the approval group or approvers are notified that the change request requires approval for the Review phase.
3. After the change request is approved, it moves into the Request for Change status and the change manager or change coordinator is notified.
4. The approval group or approvers are notified that the change request requires approval for the Business Approval phase.
5. After approval, the change request moves to the Planning in Progress status and all users assigned to the change request are notified that the change request is ready for planning.
6. The Status Reason field of the tasks gets updated to Staging in Progress and the task implementers are notified that the task group or tasks are set to Staged.
   For change requests with no tasks, only the change implementer is notified.

7. When the status reason of all the tasks is set to Staging Complete, the change request moves into the Scheduled for Review status and the change manager or change coordinator is notified that the change request is scheduled for review. If the change rule is configured to bypass the Schedule for Review status, the change request moves to the next valid status.

   Important

   This situation does not apply when Task Phase Management is enabled. For state transitions of a change request with Task Phase Management enabled, see Task-Phase-Management.

8. The approval group or approvers are notified that the change request requires approval for the Implementation Approval phase.
9. After approval, the change request moves into the Scheduled status.
   For change requests scheduled as change requests with no impact, all the users assigned to the change request are notified.
10. The status of tasks with the least sequence number is set to Assigned, if assignment has been defined. The status of tasks with no assignment is set to Pending with Status Reason Assignment (Pending for Assignment). If the least sequence number is assigned to a task group, the status of the task group is set to Work in Progress, and the status of the first child task is set to Assigned or Pending depending on whether assignment has been defined.
11. The task assignee sets the task status to Work in Progress when work begins and then updates the task information and starts implementing the task. When the first task is set to Work In Progress, the change request moves to Implementation In Progress status. The required information is automatically updated in the Actual Start Date field.
12. After last child task is set to Closed, the task group is set to Closed. When the last task of the change request is set to Closed, the change manager, change coordinator, and the change requester are notified that the change request is completed. The workflow enters the required information into the Actual End Date field.
13. The approval group or approvers are notified that the change request requires approval for the Close Down phase.
14. The change manager or change coordinator is notified when the final review is completed.
15. If a change request is canceled, the requester is notified.