Group level pipeline dashboard
Problem to solve
With #7861 (closed) we introduced the cross-project pipeline dashboard as part of the Operations Dashboard.
This provides each user with a customizable dashboard to show them the pipelines they care about. However, if as a GitLab administrator or Development Lead I've carefully created groups and sub-groups to house related projects, I may want to just quickly have a dashboard or TV monitor that shows a given groups pipelines and all of their statuses.
This would allow an increase to the usability of the Operations Dashboard by providing a convention (groups) over configuration (existing "add the projects you want") approach. This aligns this issue well with our product vision.
Kubernetesat the group level to be under
Operationsas it is at the project level
Operationsat the group level
- Link that to an automatically curated dashboard that mirrors the exisiting
gitlab.com/-/operationsdashboard, but automatically includes all projects in the group that have pipelines.
Permissions and Security
We would probably intend this to be available to anyone who can see the project's pipeline (e.g. anyone that could have added the project to their existing
/-/operations personal dashboard.
What does success look like, and how can we measure that?
We should track the usage of the specific group-level dashboard against the use of the wider personalized dashboard separately.