Edit the number of required approvals for deployments on Settings
Release notes
Follow up from #344675 (closed)
Problem to solve
As a user, I want to update the number of approvals required for executing and approving deployments in a protected environment, so that I can keep my project and team aligned with the organisation changes.
Intended users
User experience goal
The user should be able to edit the number of approvals required for a protected environment in the application's UI.
Proposal
- In the Settings > CI/CD area of a project, the user can configure Protected environments.
- If an environment has been previously protected, the user should see a dropdown button with the option to update the number of required approvals.
- Clicking the dropdown should open a list of options.
- The current selection should be highlighted/marked by default (basic dropdown behaviour)
- Clicking outside the dropdown should close it.
- If the user selects a different value in the dropdown, the new value should be automatically applied (auto save). The information should be sent to the system.
- The page does not need to reload.
Prototypes
Further details
Permissions and Security
-
Add expected impact to members with no access (0) -
Add expected impact to Guest (10) members -
Add expected impact to Reporter (20) members -
Add expected impact to Developer (30) members -
Add expected impact to Maintainer (40) members -
Add expected impact to Owner (50) members
Documentation
Yes, this will require a change to the docs on https://docs.gitlab.com/ee/ci/environments/protected_environments.html#protected-environments
Availability & Testing
Available Tier
Feature Usage Metrics
What does success look like, and how can we measure that?
What is the type of buyer?
- Alex - the Application Development Manager
- Casey - the Release and Change Management Director
- Skyler - the Chief Information Security Officer
Is this a cross-stage feature?
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.