Release

When the user representatives in the UAT stage have provided their consent, the change will move forward to the Release stage to ensure the change is accessible to all users.

 

In the release stage, the change details page will display the following tabs:

1. Details: Displays the scheduled start/end dates and the actual start/end dates of the release.  You can also add a description of the activities in the stage, attach the issues, and fill additional fields configured for the stage. Depending on your change role and permissions, you can spot-edit the fields.
2. Downtime: Displays probable downtime when releasing the change. The downtime schedule configured during the Planning stage will be shown. When a release is associated with the change, the downtime scheduled in the Release stage will be displayed as read-only information.
   
3. Associations: You can initiate and associate a release request with a change to track the deployment of the change.
   
1. Click Attach beside Associated Release.
   
2. Choose the customer from the filter in the header.
   
3. Select the releases and click Associate.
   
4. You can also create a new release request by clicking New Release. 
   

For a customer, you can associate releases created for the customer and the MSP Customer. For the MSP Customer, you can associate releases in the MSP Customer and all customer. 

1. Tasks: You can add and manage tasks in this stage.
   
2. Approvals: Track the approval levels associated with the Release stage.  
   

If no approval is added for the Release 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

• Release roles

  The release roles allow you to define access permissions to various stages in releases. You can either customize the default release roles or define new roles as required and associate these roles with users when creating a release. Association of ...

• Release Templates

  The SDAdmin can define templates for frequently created release requests by adding the required fields, auto-populating the fields, and associating users with roles. Using these templates, technicians can create release requests quickly and by ...

• Release Workflow Editor

  The Workflow Editor enables you to build a directional pathway for the release request to follow through its life cycle. The workflow editor is provided with an expandable, scrollable canvas for creating workflow diagrams and a collapsible stencil ...

• Stages and Statuses

  Release stage is a directional classification that indicates a significant event or a milestone involving a major deliverable in the release life cycle. The processes involved in the release of any deliverables, including submission, planning, ...

• Closure Codes

  Closure Code indicates the reason behind closing an release request. Technicians can specify the closure code when closing release requests to help other technicians involved in a release request understand why the release request is closed. Role ...