Value Streams Dashboard

{{< details >}}

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated

{{< /details >}}

{{< history >}}

• Introduced in GitLab 15.8 as a closed beta feature with a flag named group_analytics_dashboards_page. Disabled by default.
• Released in GitLab 15.11 as an open beta feature with a flag named group_analytics_dashboards_page. Enabled by default.
• Generally available in GitLab 16.0. Feature flag group_analytics_dashboards_page removed.
• Moved from GitLab Ultimate to GitLab Premium in 18.2.

{{< /history >}}

The Value Streams Dashboard is a customizable dashboard you can use to identify trends, patterns, and opportunities for digital transformation improvements. The centralized UI in the Value Streams Dashboard acts as the single source of truth (SSOT), where all stakeholders can access and view the same set of metrics that are relevant to the organization. The Value Streams Dashboard includes panels that visualize the following metrics:

• DORA metrics
• Value Stream Analytics (VSA) - flow metrics
• Vulnerabilities
• GitLab Duo Code Suggestions

With the Value Streams Dashboard, you can:

• Track and compare the metrics listed previously over a period of time.
• Identify downward trends early on.
• Understand security exposure.
• Drill down into individual projects or metrics to take actions for improvement.
• Understand the impact of adding AI to the software development lifecycle (SDLC) and demonstrate the return on investment (ROI) of investments in GitLab Duo.

For a click-through demo, see the Value Stream Management product tour.

To view the Value Streams Dashboard as an analytics dashboard for a group:

1. In the top bar, select Search or go to and find your group.
2. Select Analyze > Analytics dashboards.
3. From the list of available dashboards, select Value Streams Dashboard.

[!note] Data displayed on the Value Streams Dashboard is continuously collected in the backend. If you upgrade to the Ultimate tier, you get access to historical data, and can view metrics about past GitLab usage and performance.

Panels

The Value Streams Dashboard panels have a default configuration, but you can also customize the dashboard panels.

Overview

{{< history >}}

• Introduced in GitLab 16.7 with a flag named group_analytics_dashboard_dynamic_vsd. Disabled by default.
• Generally available in GitLab 17.0.
• Feature flag group_analytics_dashboard_dynamic_vsd removed in GitLab 17.0.

{{< /history >}}

The Overview panel provides a holistic view of the top-level namespace activity by visualizing key DevOps metrics. The panel displays metrics for:

• Subgroups
• Projects
• Users
• Issues
• Merge requests
• Pipelines

Data displayed in the Overview panel is collected by batch processing. GitLab stores record counts for each subgroup in the database, then aggregates the record counts to provide metrics for the top-level group. Data is aggregated monthly, around the end of the month, on a best-effort basis depending on the load on GitLab systems.

For more information, see epic 10417.

DevSecOps metrics comparison

{{< history >}}

• Contributor count metric at the group level introduced to GitLab.com in GitLab 16.9.
• Contributor count metric at the project level introduced to GitLab.com in GitLab 18.0.
• DevSecOps metrics comparison tables migrated to the ai_impact_table visualization in GitLab 18.5.

{{< /history >}}

The DevSecOps metrics comparison panels display metrics for a group or project over the past six months. These visualizations help you understand whether the key DevSecOps metrics improve month over month. The Value Stream Dashboard displays three DevSecOps metric comparison panels:

• Lifecycle metrics
• DORA metrics (Ultimate only)
• Security metrics (Ultimate only, at least the Developer role)

In each comparison panel, you can:

• Compare the performance between groups, projects, and teams at a glance.
• Identify the teams and projects that are the largest value contributors, overperforming, or underperforming.
• Drill down the metrics for further analysis.

When you hover over a metric, a tooltip displays an explanation of the metric and a link to the related documentation page.

The Change % column also indicates a percentage increase or decrease of the metric value from the previous month, compared to six months prior.

The Trend column displays sparklines to help you identify patterns in metric trends (such as seasonal changes) over time. The sparkline color ranges from blue to green, where green indicates a positive trend, and blue indicates a negative trend.

DORA Performers score

{{< details >}}

• Tier: Ultimate

{{< /details >}}

{{< history >}}

• Introduced in GitLab 16.3 with a flag named dora_performers_score_panel. Disabled by default.
• Enabled on GitLab.com in GitLab 16.9.
• Generally available in GitLab 16.11. Feature flag dora_performers_score_panel removed.

{{< /history >}}

The DORA Performers score panel is a group-level bar chart that visualizes the status of the organization's DevOps performance levels across different projects for the last full calendar month.

The chart is a breakdown of your project's DORA scores, categorized as high, medium, or low. The chart aggregates all the child projects in the group.

The chart bars display the total number of projects per score category, calculated monthly. To exclude data from the chart (for example, Not included), in the legend select the series you want to exclude. Hovering over each bar reveals a dialog that explains the score's definition.

For example, if a project has a high score for deployment frequency (velocity), it means that the project has one or more deploys to production per day.

To learn more, see the blog post Inside DORA Performers score in GitLab Value Streams Dashboard.

Filter the panel by project topic

When you customize dashboards with a YAML configuration, you can filter the displayed projects by assigned topics.

panels:
  - title: 'My dora performers scores'
    visualization: dora_performers_score
    queryOverrides:
      namespace: group/my-custom-group
      filters:
        projectTopics:
          - JavaScript
          - Vue.js

If multiple topics are provided, all topics must match for the project to be included in the results.

Projects by DORA metric

{{< details >}}

• Tier: Ultimate

{{< /details >}}

{{< history >}}

• Introduced in GitLab 17.7.

{{< /history >}}

The Projects by DORA metric panel is a group-level table that lists the status of the organization's DevOps performance levels across projects.

The table lists all projects with their DORA metrics, aggregating data from child projects in groups and subgroups. The metrics are aggregated for the last full calendar month.

You can sort the projects by metric values, helping you identify high, medium, and low-performing projects. For further investigation, you can select a project name to drill down into that project's page.

Enable or disable overview background aggregation

{{< details >}}

• Tier: Ultimate
• Offering: GitLab Self-Managed, GitLab Dedicated

{{< /details >}}

{{< history >}}

• Introduced in GitLab 16.1 with a flag named value_stream_dashboard_on_off_setting. Disabled by default.
• Enabled on GitLab Self-Managed in GitLab 16.4.
• Feature flag value_stream_dashboard_on_off_setting removed in GitLab 16.6.

{{< /history >}}

To enable or disable the overview count aggregation for the Value Streams Dashboard:

1. In the top bar, select Search or go to and find your group. This group must be at the top level.
2. Select Settings > Analytics.
3. In Value Streams Dashboard, select or clear the Enable overview background aggregation for Value Streams Dashboard checkbox.

To retrieve aggregated usage counts in the group, use the GraphQL API.

View the Value Streams Dashboard

Prerequisites:

• You must have the Reporter, Developer, Maintainer, or Owner role for the group or project.
• Overview background aggregation must be enabled.
• To view the contributor count metric in the comparison panel, you must set up ClickHouse.
• To track deployment to production, the group or project must have an environment in the production deployment tier.
• To measure the cycle time, issues must be crosslinked from commit messages.

For groups

To view the Value Streams Dashboard for a group:

• From Analytics Dashboards:
  1. In the top bar, select Search or go to and find your group.
  2. Select Analyze > Analytics Dashboards.
• From Value Stream Analytics:
  1. In the top bar, select Search or go to and find your project or group.
  2. Select Analyze > Value stream analytics.
  3. Below the Filter results text box, in the Lifecycle metrics row, select Value Streams Dashboard / DORA.
  4. Optional. To open the new page, append this path /analytics/dashboards/value_streams_dashboard to the group URL (for example, https://gitlab.com/groups/gitlab-org/-/analytics/dashboards/value_streams_dashboard).

For projects

{{< history >}}

• Introduced in GitLab 16.7 with a flag named project_analytics_dashboard_dynamic_vsd. Disabled by default.
• Feature flag project_analytics_dashboard_dynamic_vsd removed in GitLab 17.5.

{{< /history >}}

To view the Value Streams Dashboard as an analytics dashboard for a project:

1. In the top bar, select Search or go to and find your project.
2. Select Analyze > Analytics dashboards.
3. From the list of available dashboards, select Value Streams Dashboard.

Schedule reports

You can schedule reports using the CI/CD component Value Streams Dashboard Scheduled Reports tool. This tool saves time and effort by eliminating the need to manually search for the right dashboard with the relevant data, so that you can focus on analyzing insights. By scheduling reports, you can ensure that the decision-makers in your organization receive proactive, timely, and relevant information.

The Scheduled Reports tool collects metrics from projects or groups through the public GitLab GraphQL API, then builds a report using GitLab Flavored Markdown, and opens an issue in a specified project. The issue includes a comparison metrics table in Markdown format.

See an example scheduled report. To learn more, see the blog post New Scheduled Reports Generation tool simplifies value stream management.

Customize dashboard panels

You can customize the Value Streams Dashboard and configure what subgroups and projects to include in the page.

To customize the default content of the page, you need to create a YAML configuration file in a project of your choice. In this file, you can define various settings and parameters, such as title, description, and number of panels. The file is schema-driven and managed with version control systems like Git. This enables tracking and maintaining a history of configuration changes, reverting to previous versions if necessary, and collaborating effectively with team members. Query parameters can still be used to override the YAML configuration.

Before you customize the dashboard panels, you must select a project to store your YAML configuration file.

Prerequisites:

• You must have the Maintainer or Owner role for the group.

1. In the top bar, select Search or go to and find your group.
2. Select Settings > Analytics.
3. Select the project where you would like to store your YAML configuration file.
4. Select Save changes.

After you have set up the project, set up the configuration file:

1. In the top bar, select Search or go to and find the project you selected in the previous step.
2. In the default branch, create the configuration file: .gitlab/analytics/dashboards/value_streams/value_streams.yaml.
3. In the value_streams.yaml configuration file, fill in the configuration options:

# version - The latest version of the analytics dashboard schema
version: '2'

# title - Change the title of the Value Streams Dashboard.
title: 'Custom Dashboard title'

# description - Change the description of the Value Streams Dashboard. [optional]
description: 'Custom description'

# panels - List of panels that contain panel settings.
#   title - Change the title of the panel.
#   visualization - The type of visualization to be rendered
#   gridAttributes - The size and positioning of the panel
#   queryOverrides.namespace - The Group or Project path to use for the chart panel
#   queryOverrides.filters.includeMetrics - Shows rows by metric ID in the table panel.
panels:
  - title: 'Group usage overview'
    visualization: usage_overview
    queryOverrides:
      namespace: group
      filters:
        include:
          - groups
          - projects
    gridAttributes:
      yPos: 1
      xPos: 1
      height: 1
      width: 12
  - title: 'Group dora and issue metrics'
    visualization: ai_impact_table
    queryOverrides:
      namespace: group
      filters:
        includeMetrics:
          - deployment_frequency
          - deploys
    gridAttributes:
      yPos: 2
      xPos: 1
      height: 12
      width: 12
  - title: 'My dora performers scores'
    visualization: dora_performers_score
    queryOverrides:
      namespace: group/my-project
      filters:
        projectTopics:
          - ruby
          - javascript
    gridAttributes:
      yPos: 26
      xPos: 1
      height: 12
      width: 12

Supported visualization filters

The filters subfield on the queryOverrides field can be used to customize the data displayed in a panel.

DevSecOps metrics comparison panel filters

Filters for the ai_impact_table visualization.

DORA Performers score panel filters

Filters for the dora_performers_score visualization.

Usage overview panel filters

Filters for the usage_overview visualization.

Group and subgroup namespaces

Project namespaces

Additional panel filters (deprecated)

[!warning] The dora_chart visualization was deprecated in GitLab 18.5.

Filters for the dora_chart visualization.

Dashboard metrics and drill-down reports

{{< history >}}

• Code Suggestions, Non-Agentic Chat, and Root Cause Analysis usage metrics updated to display absolute user counts instead of percentage rates in GitLab 18.10.

{{< /history >}}

The following table provides an overview of the metrics available in the Value Streams Dashboard, along with their descriptions and the name of the drill-down report where they are displayed.

Metrics with Jira

The following metrics do not depend on using Jira:

• DORA Deployment frequency
• DORA Lead time for changes
• Number of deploys
• Merge request throughput
• Median time to merge
• Vulnerabilities