VSA [BE]: adding filter_by team
Problem
There is no concept of a team in GitLab.
Filtering VSA data by group label (e.g. groupoptimize) or project is too abstract and does not reflect the reality of organizations that manage and collaborate themselves across multiple dimensions. This is especially frustrating for managers, who lack a single place to answer questions like "what is my team working on?" and "how can I effectively manage resourcing now and for the future?".
Our Organization > Group > Project knowledge architecture can be classified as a vertical hierarchy.
Validation
- This Dogfooding feedback we got for VSA about the need to filter by multiple members and not the group label.
- And this Customer feedback.
For more context see the Pros & Cons of a vertical hierarchy.
Proposal
Adding to VSA data filters a new option - filter_by group_members (for example @__gitlab-org/architecture/gitlab-data-analytics/stakeholders).
This can be done by extend the GroupValueStreamAnalyticsFlowMetrics (and other endpoints) to support multiple authorUsername.