icon to create a release request by using predefined templates.Go to Releases tab and click New Release in the release list view or template view. Use the icon to create a release request by using predefined templates.
Role Required: SDAdmin, SDReleaseManager, Technicians with Create Releases permission.
Depending on the predefined template is selected, the fields and field information are auto-populated in the New Release form. If no template is selected, the default release template is used.
The workflow associated with the template is auto-selected. You can change the template and workflow if needed.
Fill out the fields displayed on the form using the following pointers:
|
Fields |
Description |
|
Release Requester |
User who requests the release process to be initiated. |
|
Type |
The business impact of the release. The SDAdmin can configure release types based on the change request under Setup > Customization > Change Management > Change Type. |
|
Impact |
Describe if the release will affect business, department, group, or user. |
|
Urgency |
Refers to how quickly the release must be completed. |
|
Stage * |
Submission will be selected by default and cannot be modified. |
|
Status * |
Requested will be selected by default and cannot be modified. |
|
Comment * |
Add any additional information related to the stage and status. |
|
Site |
Select the site where the release is scheduled. |
|
Group |
Select the technician group involved in the release. |
|
Release Engineer |
The technician who plays the central role in planning, deploying, and reviewing the release. |
|
Release Manager |
The technicians who manages the release process throughout its lifecycle. It is recommended to associate a user for this role while creating the release. |
|
Priority |
Indicate how important a release is vital to the organization. |
|
Risk |
Describe the potential threat to the organization's business functions while implementing the release. |
|
Category |
Assign a category to the release request. |
|
Sub Category |
Assign a sub-category to the release request based on the category. |
|
Item |
Assign an item to the release request based on the category and sub-category. |
|
Scheduled Start/ScheduledEnd |
The dates on which the release is planned to start and end. This is only an estimated schedule while the actual schedule may vary. |
|
Services Affected |
Lists the services that might be affected by the release. |
|
Assets Involved |
List the assets that might be involved in this release. |
|
CIs Involved |
Lists the CIs that might be involved in this release. |
|
Reason for Change |
List the reasons why the associated change had to be initiated. SDAdmins can configure reasons for change under Setup > Customization > Change Management. |
|
Title |
Add a name for the release request. (Limited to 250 characters) |
|
Description |
Provide the release details. |
|
Attachments |
Upload any related files, documents, images, or videos. |
|
Development Head |
Select the user responsible for building the service deliverable and documentation. |
|
QA Manager |
Select the user accountable for testing the service deliverable. |
|
UAT Owner |
Select the user responsible for managing UAT testing of the service deliverable. |
|
Release Reviewer |
Select the user who evaluates the entire release process after deployment. |
After specifying the release request details, click Save.
