Improve validation for minutes overflow while setting project CI/CD minutes limit
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Release notes
Problem to solve
In #357760 we've defined a workflow to control the CI/CD minutes usage per project in user namespace. To keep the scope of the MVC solution feasible, this is created as a carry over issue to refine the validation of the input while setting a limit per project.
The input for CI/CD minutes per project should be within the limit defined for the user namespace under which it is hosted.
| Image |
|---|
 |
Intended users
User experience goal
users should get clear indication of the validity of the data they input while setting the CI/CD minutes usage limit per project in a namespace.
Proposal
Add validation to the input field when user is entering the quota for the group.
If users exceed the max allotted quota for the namespace, they will see an error message Namespace CI/CD minutes quota exceeded.
Further details
Permissions and Security
Documentation
Availability & Testing
Available Tier
Feature Usage Metrics
What does success look like, and how can we measure that?
What is the type of buyer?
Is this a cross-stage feature?
What is the competitive advantage or differentiation for this 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.