OpenText Application Quality Management - Release Management Request Type

The ITIL Release Management process as modeled by OpenText Application Quality Management sends a release request of the OpenText Application Quality Management - Release Management request type along the OpenText Application Quality Management - Release Request workflow (see OpenText Application Quality Management - Release Request Workflow) to be examined and resolved.

ALM - Release Management Request Fields

Figure 3-21 shows the Create New OpenText Application Quality Management - Release Management page that appears when you create a request and select the OpenText Application Quality Management - Release Management request type. Table 3-14 describes the fields in the OpenText Application Quality Management - Release Management request, including some fields that do not appear until the request is created or until other conditions are met.

Figure 3-21. OpenText Application Quality Management - Release Management request

Table 3-14. ALM - Release Management request fields
Field Name (*Required)	Description
Summary section
Request Status	(Read-only) Status of the release request. Preset to Logged before the request is created.
Request No.	(Read-only. Added after the request is created.) Number of the request.
*Release Category	Release category, based on the scope of the release (number of changes in a release).
*Release Type	Type of release.
*Release Summary	Summary description of the release.
*Release ID (Required only after the request is created)	ID for the release.
Work Item Fields section ^a
QC/ALM Info section ^b
QC/ALM Instance	URL of the Quality Center/ALM instance with the project used for the integration.
QC/ALM Domain	Domain of the project in Quality Center/ ALM.
QC/ALM Project	Quality Center/ALM project that is integrated with this request type.
Assigned To	Developer the QC/ALM Requirement is assigned to.
Requirement No.	(Read-only) Requirement number in Quality Center/ALM.
Requirement Status	(Read-only) Status of the requirement in Quality Center/ALM.
Requirement Integration Message	(Read-only) Quality Center/ALM status message indicating success or error in the most recent operation.
Synchronize to QC/ALM Requirement	Select Yes or No radio button to indicate synchronizing to Quality Center/ALM requirement or not.
Requirement Attachment URL	(Read-only) URL of the list of attachments to the Quality Center/ALM requirement.
QC/ALM Requirement Type	Quality Center/ALM requirement type.
QC/ALM Requirement Coverage	(Read-only) The Quality Center/ALM requirement coverage
QC/ALM Open Defects	(Read-only) Number of open defects in Quality Center/ALM.
Release Planning section
*Release Definition Summary	Summary of the definition of this release.
Release Definition	Allows you to add and view the release definition document directly on the release request.
*Release Policy Summary (Required only after the request is created)	Summary of the policy that governs this release.
Release Policy	Allows you to add and view the release policy document directly on the release request.
Release Plans Summary	Summary of rollout plans for this release.
Release Plans	Allows you to add and view the rollout plans for this release (for example: a timetable of events, a resource plan, and who will do what and when) directly on the release request.
QA Information section
Release Test Plan Summary	Summary of the test plan for this release.
Release Test Plan	Allows you to add and view the release test plan (the plan that describes tests to be performed on this release in the TEST environment) directly on the release request.
Release Acceptance Criteria Summary	Summary of the release acceptance criteria for this release.
Release Acceptance Criteria	Allows you to add and view the release acceptance criteria document (which details criteria that qualify the acceptance of this release before deployment to the LIVE environment) directly on the release request.
Test Results	Allows you to add and view the test results directly on the release request.
Known Defects Summary	Summary of known defects that will be carried forward into the LIVE environment.
Known Defects	Used to specify RFCs relating to known defects that will be carried forward into the LIVE environment.
Release Preparation section
Communication Plan Summary	Summary of the communication plan for this release.
Communication Plan	Allows you to add and view the communication plan (the plan that describes the various notifications that need to be sent out prior to release deployment into the LIVE environment) directly on the release request.
Training Plan Summary	Summary of the training plan for this release.
Training Plan	Allows you to add and view the training plan (the plan that describes the training that needs to be provided prior to release deployment into the LIVE environment) directly on the release request.
Release Backout Plans Summary	Summary of the backout plans for this release.
Release Backout Plans	Allows you to add and view the backout plan (the release plan that describes procedures to back out the release to its original state) directly on the release request.
License Agreements	Allows you to add and view any license agreement documents for software licensed in this release directly on the release request.
Support Agreements	Allows you to add and view any support agreement documents for support policies of software licensed in this release directly on the release request.
Service Level Agreements	Allows you to add and view any SLAs for ordering new equipment or software directly on the release request.
Leasing Agreements	Allows you to add and view any leasing agreement documents for software leased in this release directly on the release request.
a. Fields in the Work Item Fields section are useful if you want to include Release Management requests as work items to be tracked using Resource Management. For more information, see the Resource Management User Guide. b. Fields in the QC/ALM Info section remain visible by default but are not used if OpenText PPM is not integrated with Quality Center.

Note: The administrator can remove the QC/ALM Info section from the request type by removing the QC/ALM Info field group from the OpenText Application Quality Management - Release Request Header request header type. See the Demand Management Configuration Guide for details about request header types and field groups.

How to Submit an OpenText Application Quality Management - Release Management Request

Log on to OpenText PPM.
From the menu bar, select Create > Request.

The Create New Request page appears.
On the Create New Request page, in the Request Type field, select OpenText Application Quality Management - Release Management and click Create.

The Create New OpenText Application Quality Management - Release Management page appears, displaying the appropriate release request fields.

Required fields have a red asterisk. All other fields are optional, but are often helpful when others are reviewing an open request. For information concerning a specific field, click the Help icon next to the field (if available).
Complete the fields in all sections as appropriate.

The Notes section contains fields where notes and information concerning the release can be entered and stored. Typically, when you create a release request, you do not need to add a note to it. However, add a note if you want to convey additional information to the reviewers and processors of the release request.

In the References section, you can add useful references such as a Web-accessible file or a document or file attached from a local machine. For more information about adding references, see the Demand Management User’s Guide.
On the Create New Request page, click Submit.

The release request is submitted. The Request Creation Confirmed page appears.

Note: OpenText PPM can be configured to allow you to save the request before you submit it. To have this feature enabled, see your application administrator.

After submitting the request, on the Request Creation Confirmed page you can click the link for the particular request number in the Request # field to view the detail page of the newly generated release request.

When the release request is submitted, it is assigned an initial status, such as New. The request is then routed along the OpenText Application Quality Management - Release Request workflow (see OpenText Application Quality Management - Release Request Workflow).