Update manual jobs UI across GitLab to support deployment approvals
Release notes
Problem to solve
Originally, this discussion was brought up in the first iteration for deployment approvals.
On the pipeline graph, a deployment job that is waiting for approval is currently shown like this:
Manual jobs that target protected environments use the same status representation and run button as regular manual jobs.
Once deployment approvals feature is released, this will introduce two problems:
- These jobs will show a status of “Blocked”, when the representation we chose in the environments page UI is “Waiting [Needs approval]”
- These jobs will show a regular Run button, that will automatically approve the deployment job, without giving the option to reject it.
Intended users
User experience goal
The user should be able to see a correct (and consistent) status representation for pending deployment jobs across GitLab, and be able to approve and reject them according to their needs.
Proposal
Represent the Waiting [Needs approval] status everywhere protected deployment jobs are shown, and provide the appropriate UI for approving/rejecting the job.
Further details
Permissions and Security
Documentation
Availability & Testing
Available Tier
Feature Usage Metrics
What does success look like, and how can we measure that?
Inherited from Deployment Approvals - Feature Direction (&6832):
Deployment approvals/rejections are widely adopted and usage can be measured by usage ping. Further customer research shows how users are successfully adopting this feature into their workflows, and how we can improve upon it.
What is the type of buyer?
Inherited from Deployment Approvals - Feature Direction (&6832):
Is this a cross-stage feature?
Yes, will likely need to collaborate with Pipeline Execution on this
Links / references
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.