Submission

Submission

The Submission stage involves evaluating the proposed change and its various attributes, such as impact, risk involved, urgency, priority, etc. The business requirements of the change are defined clearly.
The following tabs are displayed in this stage:
  1. Details: Displays the attributes defined while creating the change request 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. Associations: Link projects that initiated the change.
    1. Click Attach beside Projects that Initiated the Change.
    2. Choose the customer from the filter in the header.
    3. Select the projects and click Associate.
Info
For a customer, you can associate projects created for the customer and the MSP Customer. For the MSP Customer, you can associate projects in the MSP Customer and all customer. 
  1. Approvals: Track the approval levels associated with the Submission stage.
Info
 If no approval is added for the Submission stage, the Approvals tab will not be visible for this stage after the change moves to the next stage. 
  1. Status Comments: View the status transitions of the change in this stage, along with the comments added during the transitions.
 


    • Related Articles

    • Submission

      Submission stage involves initiating and evaluating a release and its various attributes, such as impact, risks involved, services affected, priority, etc. The business requirements for the proposed release are defined clearly. To view and modify the ...

    • 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 ...

    • 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 ...

    • Change Role

      Change roles define access permissions for users in the Change module. ServiceDesk Plus Cloud MSP contains default change roles that are built into the application. You can also create custom change roles. Role Required: SDAdmin Default Change Roles ...

    • Copy Changes

      Copy changes to reduce the need to create templates. You can create a new change request by making the necessary modifications to the copied change. Role Required: SDAdmin, SDChangeManager, Users with Add permission to Changes To copy a change, Go to ...