Update Project Settings to be able to set approval count
Release notes
Problem to solve
For Deployment approvals, we need some way of configuring the number of approvals required for protected environments.
Intended users
Metrics
Measuring the usage of this setting through front-end event tracking would be a good way to understand advanced usage of deployment approvals.
User experience goal
The user should be able to define how many approvals are needed to approve a manual deployment to a protected environment.
Proposal
We will add a new field called Required approvals which specifies the number of approvals from different users that are required before a deployment can continue.
Out of scope
Edit the number of required approvals #355853 (closed)
Further details
- Default value for a protected environment in a project is 0 (no approvals requires)
Technical detail
We extend Project > Settings > CI/CD > Protected Environments form.
Currently, this page is written in Haml, thus it would require a part of backend knowledge as well. This might be workable by a frontend engineer.
See the configuration page in the PoC for more details.
Permissions and Security
Documentation
Yes, documentation and screenshot for the new field in the settings page.
Availability & Testing
Available Tier
What does success look like, and how can we measure that?
Customers are able to set multiple approvals with the configuration they require.
Inherited from epic:
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 epic: