Change Request Tasks can be managed at different points in the Change Request workflow. What you can do depends on the status of the Change Request and the type of Task involved.
Adding Tasks
Both Update Document Tasks and Custom Tasks can be added to a Change Request while it is in Created or Implementing status.
For step-by-step instructions on adding each task type, refer to:
Editing Tasks
Tasks can be edited while the Change Request is in Created or Implementing status, and the tasks are in Open status. You can edit the tasks either from the Change Request Edit Form or from the task listing on the Change Request details page. A particular case of editing would be changing the due date of a task, which is covered in this article: Changing the due date of a Task in a Change Request
All fields are editable for any task type when the Change Request is still in Created status. When the Change Request is in implementing status, you can still modify all the fields for the Update Documents task, but you can only add files or modify the due date for Custom tasks.
Deleting Tasks
The ability to delete Tasks depends on the task type and the status of the Change Request.
Update Document Tasks can be selected and deleted while the Change Request is in Created or Implementing status. This action can be carried out in the Tasks Tab in the Change Request Details page or by editing through the Change Request Edit form.
Deleting tasks from the Tasks tab
Deleting tasks from the Change Request Edit form
Custom Tasks can be deleted while the Change Request is in Created status. Once the Change Request moves further in the workflow, Custom Tasks can no longer be deleted — even by Administrators.
If a Custom Task is no longer relevant once the Change Request is in Implementing status, it should be marked as closed instead. When signing off, the Responsible User can enter a Remark explaining the rationale. This remark will be included in CR reports if the variable ${cr_custom_tasks} is used.
This behaviour is by design. Update Document Tasks are linked to the Document Control module, where documents follow their own approval workflow and audit trail — the system allows flexibility here because document-level traceability is maintained independently. Custom Tasks, on the other hand, are fully contained within the Change Request itself. Restricting deletion once implementation is underway ensures that all roles involved in the Change Request — Approvers, QA, and Responsible Users — are working from the same agreed scope, preserving a complete and trustworthy record of what was planned and executed.