Improve the pattern for shared runner usage in group usage quota page
Release notes
Problem to solve
The usage quota pages on the group and user namespace level look different today. Recently there were changes made to how we show the shared runner usage information to users on the usage quota page through !83224 (merged). The latest design was worked on keeping in mind the use cases for that would allow users make the best use of this information.
However, on the group quota page we still use the old pattern.
Group Usage Quota | User-namespace usage Quota |
---|---|
![]() |
![]() |
the designs for both the usage quota pages are different.
Intended users
User experience goal
Users should not see different pattern for displaying shared runner usage information on group vs user namespace usage quota page.
Proposal
Replicate the pattern showing shared runner usage from user-namespace to group usage quota page
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?
No
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.