Close

Close

In the final stage, the change request is closed after assigning it an appropriate closure code which indicates whether the change was approved, rejected, or closed halfway. Learn more about closure code.
 
The following tabs are displayed:
  1. Details: Displays the closure code, description, attachments, and additional fields configured for the stage. Depending on your change role and permissions, you can spot-edit the fields.
  2. Tasks: You can add and manage tasks in this stage.
  3. Approvals: Track the approval levels associated with the Close stage.
Info
The Approvals tab will be visible for the Close stage when the change is in the stage, and after the change is closed.
  1. Status Comments: View the status transitions of the change in this stage, along with the comments added during the transitions.


    • Related Articles

    • Close Changes

      Role Required: SDAdmin, SDChangeManager, Users with Approve permission to the current stage and the Close stage. You can close changes from the list/template view or the change details page. To close changes in bulk, select the preferred changes from ...

    • Close Requests

      Requesters and technicians can close requests that have been addressed and resolved. Role Required: Technicians with Close Request permission; Requesters Closing a Request as a Requester A requester can close a resolved request by opening it and ...

    • Closure

      The life cycle of any release process, be it a completed or a canceled one, ends with the closure stage. In this stage, the release coordinator associates a closure code for the release. The closure code provides details on whether the release is ...

    • Pick Up Changes

      Role Required: SDAdmin, SDChangeManager, Technicians with Edit permission to the respective change stage Technicians associated to the respective customers can pick up unassigned changes from the list/template view. This reduces the waiting time to ...

    • Closure Rules Use Cases

      Closure Rules Pointers Closure rules automate the collection of vital details and execute relevant actions before a record can be closed in the service desk. Closure rules are not customer-specific. Supported Modules: Requests, Problems, Changes, ...