GitLab Dashboard Foundations Roadmap
## Quick overview
### Current Status (as of Jan 2026)
- :white_check_mark: [Layout Framework](https://design.gitlab.com/patterns/dashboards/): Production-ready, adopted by Security, Compliance, Analytics dashboards
- :white_check_mark: [Data Analyst Agent](https://docs.gitlab.com/user/duo_agent_platform/agents/foundational_agents/data_analyst/) in beta (18.7), driving to GA.
- :construction: Customization:
- [x] Architecture document for [Dashboard Customization Framework](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/dashboard_customization_framework/) complete.
- [ ] Storage API in progress by ~"group::platform insights" ~backend engineers
- [ ] Next: Release dashboard customization to customers
- :construction: Data Exploration:
* [x] https://gitlab.com/groups/gitlab-org/-/epics/19500+
* [x] https://gitlab.com/groups/gitlab-org/-/work_items/20337+
* [ ] https://gitlab.com/groups/gitlab-org/-/work_items/21876+s
- :construction: Navigation:
* [ ] [New dashboard space](https://gitlab.com/groups/gitlab-org/-/work_items/20765)
* [ ] Depends on Cells/Organizations (ETA FY27)
### Components
Our dashboard foundation can be broken down into 4 pillars ([issue board](https://gitlab.com/groups/gitlab-org/-/boards/9349401)). See the [architecture](#architecture) section below to learn more.
| Framework Pillar | Status | When can I use this?\* |
|------------------|--------|------------------------|
| **Layout framework** | Ready to use :white_check_mark:<br>- [Developer docs](https://docs.gitlab.com/development/fe_guide/dashboard_layout_framework/)<br>- [Pajamas dashboard guidelines](https://design.gitlab.com/patterns/dashboards/)<br>- [GitLab-UI dashboard components](https://design.gitlab.com/storybook/?path=/docs/dashboards-dashboards-layout--docs) | FY26 Q2 |
| **Customization** | In development <br>- :construction: https://gitlab.com/groups/gitlab-org/-/epics/19430+s | FY27 Q1/Q2 |
| **Data exploration** | Done: <br>- :white_check_mark: https://gitlab.com/groups/gitlab-org/-/epics/19500+ <br>- :white_check_mark: https://gitlab.com/groups/gitlab-org/-/work_items/20337+ <br>In development <br>- :construction: https://gitlab.com/groups/gitlab-org/-/work_items/21876+s | FY27 Q1 |
| **Navigation & Migration** | In development <br>- :construction: https://gitlab.com/groups/gitlab-org/-/work_items/20765+s | FY27 Q2 |
**Note:** Timelines are subject to change. See the strategic roadmap below for additional details.
---
## Dashboard Foundation: Enabling Self-Service Analytics at Scale
### Problem to solve
Dashboards at GitLab have always been inherently feature-focused, without clear UX guidance or common UI framework instructing how to build a dashboard. The result is an inconsistent UX and code that is spread out and costly to maintain.
The legacy dashboard development flow:
```mermaid
graph LR
A["No clear UX guidelines"] --> B["Built using bespoke solution"]
B --> C["Costly to maintain and upgrade"]
classDef problem stroke:#be185d,stroke-width:2px
class A,B,C problem****
```
Negative impact:
- :chart_with_downwards_trend: Large [list](https://docs.google.com/spreadsheets/d/1dCJFJNKl0OF7OhOXR4FWNwLVUGUh71NxeimFjq1cTz0/edit?gid=0#gid=0) of bespoke dashboards
- :chart_with_downwards_trend: Inconsistent UX for customers
- :chart_with_downwards_trend: We struggle to share and build upon each other's progress
- :chart_with_downwards_trend: We cannot ship Duo or other advanced features across the board
### Proposal
Transform GitLab's analytics landscape by establishing a comprehensive Dashboards-as-a-Service (DAAS) framework that empowers our product teams, customers, and Duo to easily find, query, and surface the most relevant data.
Ideal dashboard development flow:
```mermaid
graph LR
A["Design using guidelines"] --> B["Build using UI components"]
B --> C["Get improvements downstream"]
classDef solution stroke:#059669,stroke-width:2px
class A,B,C solution
```
Aimed impact:
- :chart_with_upwards_trend: Efficiency for designers, with shared Pajamas and Figma dashboardcomponents
- :chart_with_upwards_trend: Efficiency for engineers, with common UI components that deliver a great UX
- :chart_with_upwards_trend: Accelerates us to ship Duo and powerful analytics features across all dashboards
**How?** Create the foundational infrastructure to support GitLab's extensive dashboard ecosystem in several iterations. Starting with the most common and critical use-case (static dashboards) and then to move on to more advanced dashboard features like customization and AI-powered data exploration to enable customers to self-service their own analytics needs. While ~"group::platform insights" is leading the development of this foundation, we should also enable adopters or interested parties to become co-owners by providing clear guidance on how and where to collaborate.
The dashboard foundation should enable:
- Product teams to focus on the data and how it's presented, rather than how to build dashboards from scratch.
- Customers to self-service their own analytics needs in a consistent dashboard experience across the platform.
- Duo to help users explore which data they have available across the platform and visualize it.
### Strategic Roadmap
<table>
<tr>
<th></th>
<th>FY26 Q2</th>
<th>FY26 Q3</th>
<th>FY26 Q4</th>
<th>FY27 Q1</th>
</tr>
<tr>
<td>
**Layout framework**
</td>
<td>
**Shared library delivered.** Impact:
* [Published developer guides and docs](https://docs.gitlab.com/development/fe_guide/dashboard_layout_framework/)
* [UX guidelines published](https://design.gitlab.com/patterns/dashboards/)
* [Shared UI components created](https://design.gitlab.com/storybook/?path=/docs/dashboards-dashboards-layout--docs)
* [Compliance, Security, and Analytics dashboards using framework](https://gitlab.com/groups/gitlab-org/-/epics/18455)
</td>
<td colspan="3">
**Grow impact**<br>Onboard more teams and migrate dashboards →
</td>
</tr>
<tr>
<td>
**Customization**
</td>
<td></td>
<td>
**Storage API**<br>Cells compatible
</td>
<td>
**User interface**<br>CRUD dashboards
</td>
<td></td>
</tr>
<tr>
<td>
**Data exploration**
</td>
<td></td>
<td>
**GLQL powered MVC**<br>MR analytics
</td>
<td>
**Duo analytics MVC**<br>Empower Duo to answer analytical questions
</td>
<td>
**Add data sources**<br>Onboard more categories
</td>
</tr>
<tr>
<td>
**Navigation**
</td>
<td></td>
<td></td>
<td></td>
<td>
**Hierarchy separation**<br>Bring dashboards to the organizational level
</td>
</tr>
</table>
_Note: Timelines are subject to change_
#### Our focus for FY26 Q3
We need to make significant progress on customization and data exploration while driving impact through framework adoption. Here are our goals ordered by priority:
<details>
<summary>List of tasks</summary>
:construction: Issues for each target is WIP and will be added soon :construction:
1. :mag: \*\*Data exploration | Nascent (1/4) → Limited (2/4) | High priority | \*\*[**Epic**](https://gitlab.com/groups/gitlab-org/-/epics/17818)
- [x] Finalize UX designs for first iteration (https://gitlab.com/gitlab-org/gitlab/-/issues/556566)
- [x] Add support for visualizing charts in GLQL query (https://gitlab.com/gitlab-org/gitlab/-/issues/560285)
- [ ] Add MR analytics to GLQL data sources
- [ ] Deliver MVC data explorer powered by GLQL
- [ ] Add support for GLQL to dashboard panels (https://gitlab.com/gitlab-org/gitlab/-/issues/556730)
2. :art: **Customization | Nascent (1/4) → Limited (2/4) | High priority**
- [x] Complete research into storage options (https://gitlab.com/gitlab-org/gitlab/-/issues/555058)
- [ ] Deliver an API to CRUD custom dashboards on organization level
- [ ] Finalize UX designs for dashboard editor MVC
3. :results: **Grow dashboard framework impact | Medium priority**
- [ ] Grow awareness of dashboard framework (broadcast, recordings)
- [ ] Add contribution guide to expand framework ownership
- [ ] Migrate 1 high usage (MAU) legacy dashboards to framework (https://gitlab.com/gitlab-org/gitlab/-/issues/560339)
- [ ] Migrate 2 "low-hanging fruit" legacy dashboards to framework (https://gitlab.com/gitlab-org/gitlab/-/issues/555049)
4. :efficiency: **Continue to refine dashboard framework subcomponents | Medium priority**
- [ ] Gain user feedback and insight (https://gitlab.com/groups/gitlab-org/-/epics/18455)
- [x] Add panel component to Pajamas (https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/1643)
- [x] Add dashboard filter guidelines (https://gitlab.com/gitlab-org/gitlab/-/issues/521751)
- [ ] Add dashboard panel filter guidelines
- [ ] Update framework to match latest UX designs (https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/issues/2956)
</details>
#### Proposed prioritized goals for FY26 Q4
1. **Layout framework** reaches maturity of Great (4/4) to enable self-service development for static-dashboards across GitLab
2. **Data exploration** reaches maturity of Useful (3/4) to enable customers to explore their data on available data source.
3. **Customization** reaches maturity of Useful (3/4) to enable customers to surface relevant data across multiple data sources.
4. **Navigation** stays at Limited (2/4) and we have plans in place to enable users to builds dashboards at the organizational level.
##### Vision for FY27 and beyond
- **Layout framework**: Owned and worked on by multiple teams and community contributors.
- **Data exploration**: Duo powered data explorer that's available across the GitLab application.
- **Customization**: Teams & customers can easily build, modify and dashboards with visualizations most relevant to them.
- **Navigation**: Have dashboards of any scope available at the organization level, enabling customers to have a birds eye view and see the most relevant data across their entire organization.
### Architecture
Our guiding principle for the framework is [convention over configuration](https://handbook.gitlab.com/handbook/product/product-principles/#convention-over-configuration) to ensure dashboards across GitLab have UI consistency and deliver a high quality experience. While the framework enforces strict conventions for dashboard and analytical feature behaviours, its contents should remain fully configurable, allowing feature teams and users to define their own [grid](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/dashboard_layout_framework/#the-grid) layout and [panel](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/dashboard_layout_framework/#panels) contents within the structured framework.
The foundation can be split into two categories: navigation & dashboards. While navigation is a standalone pillar, the dashboard framework can be further split into 3 pillars: layout framework, customization, data exploration. Like an onion, each layer of the foundation builds upon the previous to add additional features with increased complexity. Adopters of the framework need only adopt the core layout framework for a standard static dashboard experience. Additional features like user customization and data exploration are optional, but ultimately needed to enable customers to self-service their own analytics needs.
_Diagram showing the two categories: navigation & dashboards._
#### Architecture design documents
* [Dashboard Layout Framework](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/dashboard_layout_framework/)
* [Dashboard Customization Framework](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/dashboard_customization_framework/)
* [GitLab Data Exploration and Querying Architecture](https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/gitlab_data_exploration/)
### Framework pillars
#### **<span dir="">1. </span>:construction_site:<span dir=""> Layout Framework</span>**
> Primary Focus: **Establish the gold standard for dashboard layouts**
Related epic: https://gitlab.com/groups/gitlab-org/-/epics/17819+
Already adopted the layout framework:
* ~"group::optimize" [Analytics dashboards](https://gitlab.com/groups/gitlab-org/-/analytics/dashboards)
* ~"group::security insights" [New security dashboard](https://gitlab.com/groups/gitlab-org/-/epics/16517)
* ~"group::compliance" [Compliance center dashbaord](https://gitlab.com/gitlab-org/gitlab/-/issues/543947)
For an up to date list with more details see this [epic](https://gitlab.com/groups/gitlab-org/-/epics/18455).
<details>
<summary>Click to expand</summary>
**Why This Matters:**
- Enables rapid migration of GitLab's extensive and dispersed dashboards
- Reduces cognitive load for teams adopting the framework
- Creates consistent user experience across dashboards using the framework
**Business Impact:**
- :chart_with_upwards_trend: **UI/UX Consistency** across GitLab's entire analytics ecosystem
- :chart_with_upwards_trend: **Reduced development & maintenance cost** for dashboards using our framework
- :chart_with_upwards_trend: **Easy upgrade path** to more advanced features, such as customization and data exploration
**Requirements:**
- Teams have existing dashboards OR want to create new ones
- Minimal technical overhead for adoption
</details>
#### 2. :art: Customization
> Primary Focus: **Empower users to tailor dashboards to their unique workflows**
<details>
<summary>Click to expand</summary>
**Why This Matters:**
- Known demand from Optimize, Analytics, Security, and Personal Productivity teams
- Users need flexibility to surface data relevant to their specific roles
- Foundation for future advanced personalization features
**Aimed Business Impact:**
- :chart_with_upwards_trend: **Increased user engagement** through personalized experiences
- :chart_with_upwards_trend: **Make GitLab less confusing** by consolidating multiple analytics features into a single view
- :chart_with_upwards_trend: **Improved data-driven decision making** with relevant data surfacing
**Requirements:**
- Must use the dashboard layout framework
- Dashboard customization guidelines to Pajamas
- Fully integrated with data explorer experience
- Have infrastructure in place to store dashboard configurations with appropriate auth
</details>
### 3. :mag: Data Exploration
> Long-term vision: **Enable customers to interact with and visualize all their data from a single interface**
<details>
<summary>Click to expand</summary>
**Why This Matters:**
- GitLab's data is scattered across multiple surfaces and formats
- Users struggle to get holistic views of their workflows
- Need single query language and interface for data exploration
**Strategic Approach:**
- :dart: **Start Small:** Focus on key data sources and GLQL integration
- :books: **Enable Teams:** Provide tools, examples, and documentation
- :recycle: **Iterate Based on Usage:** Let real use high value cases to drive development
**Business Impact:**
- :chart_with_upwards_trend: **Increased Platform Power** and usability
- :chart_with_upwards_trend: **Better Data Discoverability** across GitLab
- :chart_with_upwards_trend: **Faster Insights** for users at all levels
**Requirements:**
- Data sources accessible via a single query langauge (GLQL)
- Robust querying and filtering capabilities
- Intuitive user interface for non-technical users
- Can export their query visualizations to custom dashboards
- Fully integrated with Duo to explore and gain understanding
</details>
#### 4. :compass: Navigation
> Primary Focus: **Solve the hierarchy problem in GitLab analytics**
Related epic: https://gitlab.com/groups/gitlab-org/-/epics/13798+
<details>
<summary>Click to expand</summary>
**Why This Matters:**
- Group-level dashboards currently provide _less_ visibility than project-level
- Large organizations need consolidated views across multiple projects
- Current Analytics and Optimize consolidation under "Analyze" needs better structure
**Business Impact:**
- :chart_with_upwards_trend: **Enterprise User Empowerment** for multi-project oversight
- :chart_with_upwards_trend: **Centralized Data Access** for decision makers
- :chart_with_upwards_trend: **Streamlined Workflows** for complex organizational structures
**Blocked by Cells implementation**
- :warning: The use of the organization hierarchy model to place the dashboards listing page for all groups and projects _within the org_ at the top of the org hierarchy.
- :warning: API integration to the org
- :warning: UI/UX considerations and placement of the dashboards listing page within the new org UI.
**Requirements:**
- Project-level data queryable at group and organization level
- Adequate filtering, performance, and formatting capabilities
- Scalable architecture for large datasets
</details>
**Legend:** Nascent (1/4) → Limited (2/4) → Useful (3/4) → Great (4/4)
epic