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, schedules, before approving then and moving the release to the Test Approval phase.
The read-only Approval Phase field shows what approval phase the release is in during its life cycle.
The application administrators configure the approval processes. The process owner determines the approvals based on the policies of the business. They determine which release requests require approval, what kind of approval process the release requests must undergo, and who the approvers are. Support staff and management can add more approvers to the list.
Related topics
Approving or rejecting requests
Resubmitting a rejected request
Approving or rejecting requests via email
Comments
The details and diagrams around Release approval contradict each other. In some parts of the documentation text and diagrams it shows that the approval happens at the beginning of the milestone, while other text and diagrams show the exact opposite.
For example, on this page you have the following statement, "After a release is planned and built, the release request is set to a status of Build Approval if approval is configured."
In actuality, the release request cannot be built until after it has passed the Build Approval, if the approval is configured.
Log in or register to comment.