This documentation supports the 9.1 version of Change Management.

To view the latest version, select the version from the Product version menu.

Implement stage - Working on task assignments

Following the recommended life cycle of a change request, the status of a task should be in Scheduled before you accept the task. You cannot start working on a task until the change request reaches the Implement stage. For more information, see User roles in the change request lifecycle.

You receive notification of assigned tasks by Remedy Alert, email, and so on. You can also use the Overview Console or the Change Management Console to view all tasks assigned to you. The table list includes a column that shows the assignee of the task. Tasks are identified by the TAS prefix. To access the Change Management console, the task implementer must have Infrastructure Change Master, Infrastructure Change User, Infrastructure Change Submit, or (at a minimum) Infrastructure Change Viewer permissions.


Tasks do not support functional roles; they have their own permission model. Remedy Change Management maps its groups into the relevant task computed groups for access. For this reason, users with Infrastructure Change Viewer permission cannot update the task assigned to them from the parent change request. To work on a task with Infrastructure Change Viewer permission, you must also be assigned a functional role (for example, Infrastructure Change Coordinator) and you must open the task from the Change Management console.

Was this page helpful? Yes No Submitting... Thank you