Environment Approval Workflow Unusable

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Release notes

Problem to solve

If a dev wants to deploy release pipeline created some time in past, they currently go to the job, and it is expected there is some Approval workflow that can be kicked off. Instead, it says Waiting for Approvals. If they are not a Maintainer or above, they can't even see who the approvers are. So right now they have to ask around the team. (fixed in #383411 (closed))

Once they find the approver, they have to ask that person through email/IM/manual method outside of Gitlab, point them to the specific job and environment and ask them to Approve.

Approvers then get to the same page with "View Environment Details Page" link - from the job itself. If click on this link, it doesn't filter for that job, it shows ALL jobs. There's no way to filter to it. Sometimes there are 50 pages of jobs.

Approver has to scroll through to find the job manually.

See screenshots below

Original description

Please see Environment Approval Workflow Unusable – GitLab, Inc. for the details. I also entered them in my Edifecs Gitlab Support Project here for my own ease of understanding where our features are in terms of processing. That link is here: Environment Approval Workflow Unusable (#17) · Issues · GitLab.com / account-management / Commercial / Edifecs Inc · GitLab

Proposal

Add a button to the approvals page that sends a configured notification to the approvers.

The notification can be configured to be

  • an e-mail (default)
  • a Slack message
  • a GitLab TODO

The notification should contain information and a direct link to the approval page of the given deployment.

Intended users

Feature Usage Metrics

  • MAU who trigger a notification to be sent

Does this feature require an audit event?

No.

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.

Edited by 🤖 GitLab Bot 🤖