This documentation supports the 21.3 version of BMC Helix ITSM: Change Management. To view an earlier version, select the version from the Product version menu.

Approving release requests

Release Management approvals are similar to the Change Management approvals. 

This topic provides information about the out-of-the-box approval processes provided for Release Management.

Related topics

The following topics described for Change Management approvals are also applicable for Release Management:

Understanding the Release Management approval process

After a release is planned and built, the release request is set to a status of Scheduled for Review. The release coordinator has the opportunity to review plans and schedules before moving the release to the Implementation Approval phase.

The read-only Current Approval Phase field displays what approval phase the release is in during its lifecycle.


Working with release request approvals

Certain release requests must pass through an approval process before they can be deployed. Approvals can be defined for each milestone of the release request from Initiate to Close Down.

After a release is planned and built, the release request is set to a status of Build Approval if approval is configured. The Release Coordinator has the opportunity to review plans and schedules before approving them and moving the release to the Test Approval phase.

The read-only Approval Phase field displays what approval phase the release is in during its lifecycle.

The application administrators configure the approval processes. The process owner determines the approvals based on the policies of the business. They also determine which release requests require approval, what kind of approval process the release requests must undergo, and who the approvers are. The support staff and management can add more approvers to the list.


Approval processes provided out-of-the-box for Release Management

Release Management is installed with default approval processes designed for out-of-the-box for global use.

Approval process (phase)

Definition

Initiate

The Initiate phase starts when the release request is placed in Initiation Approval status.

  • If the release request is approved, the request moves to the Registered status.
  • If the release request is rejected, its status changes to Rejected.
  • If there are no approvers defined for the request (that is, if no approvers are mapped to the Initiate approval phase), its status changes to Registered and it requires the release coordinator to move the request forward.

Planning

The Planning phase starts when the release request is placed in Planning Approval status.

  • If the release request is approved, it moves to the In Progress status.
  • If no approvers are mapped to the Planning phase, the release request moves to the In Progress status and it requires the release coordinator to move the request forward.
  • If the request is rejected, it moves to the Rejected status.

Build

The Build phase starts when the release request is placed in Build Approval status.

  • If the release request is approved, it moves to the In Progress status.
  • If no approvers are mapped to the Build phase, the release request moves to the In Progress status and it requires the release coordinator to move the request forward.
  • If the request is rejected, it moves to the Rejected status.

Test

The Test phase starts when the release request is placed in Test Approval status.

  • If the release request is approved, it moves to the In Progress status.
  • If no approvers are mapped to the Test phase, the release request moves to the In Progress status and it requires the release coordinator to move the request forward.
  • If the request is rejected, it moves to the Rejected status.

Deployment

The Deployment phase starts when the release request is placed in Deployment Approval status.

  • If the release request is approved, it moves to the In Progress status.
  • If no approvers are mapped to the Deployment phase, the release request moves to the In Progress status and it requires the release coordinator to move the request forward.
  • If the request is rejected, it moves to the Rejected status.

Close Down

The Close Down phase starts when the release request is placed in Close Down Approval status.

  • If the release request is approved, it moves to the Completed status.
  • If no approvers are mapped to the Close Down phase, the release request moves to the Completed status.
  • If the request is rejected, it moves to the Rejected status.


Important

You can view the included approval phases on the Status Flow tab of the Approval Process Configuration form. For information about configuring approvals as an administrator for Change Management, see Configuring approval processes.

For information about working with the Approval Server as an administrator, see Approval roles Open link in the Action Request System documentation.

To view release requests awaiting approval from the Release Management console

Release coordinators submit the requests for approval and monitor the approval process. Approvers are notified when a release request requires their approval. After reviewing the release request, they can approve it or reject it.

As an approver, you are required to review release requests for approval. You review release requests and provide approval through the Release Management application or Approval Central.

To view the release requests awaiting approval from Approval Central, click Pending Approvals under the Approval Tasks list of Approval Central.

  1. In the Release Management console, under Counts in the left navigation pane, click Waiting Approval.
    The Releases table displays the release requests waiting approval.
  2. Select the release request to review, and then click View.
    The approver can approve or reject the release request from the Release Request form, or request further information.
Was this page helpful? Yes No Submitting... Thank you

Comments