Dashboards should be available at an organization level

Problem

Current State

GitLab currently provides analytics dashboards at three distinct levels:

  • Instance level (/-/analytics/dashboards)
  • Group level (/groups/group/-/analytics/dashboards)
  • Project level (/project/-/analytics/dashboards)

Core Problems

  1. Fragmented Data Views: Users must navigate between multiple tabs to view reports across different groups, creating an inefficient workflow.
  2. Inconsistent Experience: The user experience differs between group and project-level dashboards, making it harder for users to switch contexts.
  3. Limited Data Aggregation: There is no capability to aggregate or roll up metrics across multiple groups, a feature repeatedly requested by customers.

This aggregation limitation extends beyond dashboards and affects other GitLab features, as documented in the broader discussion about hierarchical data visualization (issue: Problems with GitLab's Knowledge Architecture (#467558)).

The lack of cross-group data aggregation forces users to manually compile insights across organizational boundaries, impacting their ability to gain comprehensive visibility into their metrics.

Supporting research / feedback (WIP)

  • ...
  • ...

Proposal

Limiting the scope of this problem to Dashboards — Ideally there would be a single place to navigate to in GitLab to see all dashboards that a user has permissions to. Similarly, for users that just want to explore what data is available, there should be a single place to navigate to and filter and aggregate data across projects and groups.

Possible solution 01 (Your work)
Proposal_01
  • Update the navigation under "Your work"

Questions

  • Where would be the best place in the navigation to add these items?
  • How are other groups within the Plan stage approaching this problem?
  • How does the Cells team work overlap?
Edited by Libor Vanc