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.

Configuring release management approval mappings

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

The preconfigured approval processes are defined in the following table:

Approval Phase

Process

Definition

Initiate

Release Level CI - Initiate

Used with Configuration Items on the Approver Mappings form. This level of the approval process occurs when the release reaches the Review phase.

  • If approved, the release moves to the Planning Approval Phase.
  • If no approvers are mapped, the release moves directly to the Planning Approval Phase and requires the release coordinator to move the release forward.

    By default, the status of this approval process for this phase is Enabled.

Planning

Release Level CI - Planning

Used with Configuration Items on the Approver Mappings form. 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 requires the release coordinator to move the request forward.
  • If the request is rejected, it moves to the Rejected status.

    By default, the status of this approval process for this phase is Enabled.

Build

Release Level CI - Build

Used with Configuration Item on the Approver Mappings form. The Build phase starts when the release request is placed in Build Approval status.

Test

Release Level CI - Test

Used with Configuration Items on the Approver Mappings form. 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 requires the release coordinator to move the request forward.
  • If the request is rejected, it moves to the Rejected status.

    By default, the status of this approval process for this phase is Enabled.

Deployment

Release Level CI - Deployment

Used with Configuration Items on the Approver Mappings form. 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 requires the release coordinator to move the request forward.
  • If the request is rejected, it moves to the Rejected status.

    By default, the status of this approval process for this phase is Enabled.

Close Down

Release Level CI - Close Down

Used with Configuration Items on the Approver Mappings form. 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.

    By default, the status of this approval process for this phase is Enabled.

Release Management also includes approval processes for general releases and changes associated with CIs, as described in the following table:

Approval Phase

Process

Works with which approver mappings

Initiate

Release Level - Initiate

Basic approval process. Can be used with fields configured on the Categorization, Role, and Advanced Criteria tabs on the Approver Mappings form.

Planning

Release Level - Planning

Basic approval process. Can be used with fields configured on the Categorization, Role, and Advanced Criteria tabs on the Approver Mappings form.

Build

Release Level - Build

Basic approval process. Can be used with fields configured on the Categorization, Role, and Advanced Criteria tabs on the Approver Mappings form.

Test

Release Level - Test

Basic approval process. Can be used with fields configured on the Categorization, Role, and Advanced Criteria tabs on the Approver Mappings form.

Deployment

Release Level - Deployment

Basic approval process. Can be used with fields configured on the Categorization, Role, and Advanced Criteria tabs on the Approver Mappings form.

Close Down

Release Level - Close Down

Basic approval process. Can be used with fields configured on the Categorization, Role, and Advanced Criteria tabs on the Approver Mappings form.

Any phase

Release Management Chain

The Parent-Child process type uses the manager of the release requester as the approver. Based on the levels of approval defined, the process selects approves based on the requester's manager, or the manager's manager. This approval is not configured for use out of the box.

Any phase

Release Ad Hoc

This process provides routing authority to each approver without requiring the administrator to create approver mappings for every individual or group. The Release Ad Hoc approval process can be used in any phase.

For Release Management, the release coordinator is the first approver.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*