Create a Release Request
Initiate a release by raising a release request with all relevant details, such as the reason for initiating, impact, risks involved, services affected, priority, and more.
You can raise a release request with or without associating any change records in the application. When associated, the release process will be in sync with the change management process throughout its lifecycle.
Role Required: SDAdmin, SDReleaseManager, or technicians with Add Releases permission. To create a release request,
- Go to the Releases module.
- Choose all or a specific customer from the drop-down in the header.
- Click New Release. Use the drop-down menu
next to the New Release button to choose a release template for request creation.
- Enter the following details: (* Mandatory)
Fields | Description | Configuration |
Template | Use release templates to auto-populate form fields and create requests quickly for repetitive and emergency releases. | Choose a release template from the drop-down on the top. The form fields will load based on the chosen template. |
Workflow | Define a workflow for release processes specific to the customer's objectives. Associate a workflow with the release request to help technicians understand its lifecycle and processes involved. | Select the required workflow from the drop-down on the top. |
Release Requester | Release Requester is the one who initiates the release. | Choose the requester from the drop-down. |
Type | Categorize a release based on the business impact and determine whether the process is a major, minor, standard, or significant one. They play a vital role in deciding the template and workflow for the release. | Choose a release type from the drop-down. |
Site | - | Select a site that might get affected by the release. |
Group | - | Select the group in-charge for the release. |
Release Engineer | Responsible for the technical execution of the release process. | Select the technician from the drop-down. |
Release Manager | Oversees and coordinates throughout the release life cycle. | Select the technician from the drop-down. |
Stage * | A release milestone adhering to ITSM standards. | Submission stage is set by default for release request creation. |
Status * | Set the progress of the stage. | Requested status is set by default for release request creation. |
Status Comment | - | Provide additional information about the release stage status. You can edit the comment after every status update. |
Risk | Define the potential failure and uncertainties revolve around the release. | Select the risk level from the drop-down. |
Impact | Define the effect or consequence a release can have on a business level. | Select the impact from the drop-down. |
Urgency | Define how soon the release must be implemented. | Select the urgency from the drop-down. |
Priority | Define the importance of the release. | Set the priority using the drop-down. |
CSI Section | Classify the release. | Select the relevant category, subcategory, and item. |
Scheduled Start | Define the release schedule. | Specify the release schedule period using the calendar. |
Scheduled End | ||
Services Affected | Specify the services affected by the release. | Select the relevant services from the picklist. |
Assets Involved | Specify the assets affected by or associated with the release. | Select the relevant assets from the picklist. |
CIs Involved | Specify the configuration items affected by or associated with the release. | Select the relevant CIs from the picklist. |
Reason for Change | - | Select the release for release from the drop-down. To create custom reasons, go to Setup > Customization > Change Management > Reason for Change. |
Title * | - | Give the release a title. |
Description | - | Describe the release. |
Attachment | Provide release-relevant files, documents, images, and videos, if any. | Drag and drop the files from your computer. Or, click the Maximum size: 50 MB |
Roles | Assign users/technicians the appropriate roles for managing the release process. | Select the relevant users/technicians for the corresponding roles from the picklist. |
- Click Save.
Related Articles
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 ...Release Views
Releases List View The releases list view is a tabular view that displays release requests and their attributes as columns. By default, release requests are displayed in the list view. Choose all customers or a specific customer from the drop-down in ...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 Execution
Release workflow provides a detailed execution flow of a release process within an organization. To learn how to configure a workflow, refer to the release workflow editor. Role Required: Users with the View Releases permission. To view the workflow ...View Release Details
Go to Releases and click the required release in the list to view its details. On the details page, you will find all the details provided while creating the release request. Users can spot edit fields in the details page, provided they have the ...