User Should Be Able to Self Approve Deployment after Manual Job is Played
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Release notes
When a user defines a job as when:on_success and when:manual and has deployment approvals the approval panel should not be visible before someone has pressed the play button when the job is configured to be when: manual. Moreover, the the user should be able to approve their own deployments.
Problem to solve
If the environment is not setup to be protected with approval, the job will run automatically, but with approval setup, it will wait for approval. The user who submitted the pipeline is unable to self-approve the deployment.
This appears to be the same behaviour with on_success and manual.
Right now the only way to accomplish this now is two use a second project.
First from the manual job to this “second project”, Every user should be able to do that from the “main” project. In the “happy path”, the triggered pipeline in the second project would run successfully and trigger the continuation of the pipeline in the main project (or a child pipeline maybe?). In the “unhappy path”, the triggered pipeline in the second project would fail to run because the triggering user doesn’t have permissions to run pipelines in the second project. because of the two projects, you have two different user sets that you can manage as you wish.
Proposal
Intended users
Feature Usage Metrics
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.