Value Stream Analytics

Version history

Value Stream Analytics measures the time spent to go from an idea to production (also known as cycle time) for each of your projects or groups. Value Stream Analytics displays the median time spent in each stage defined in the process.

Value Stream Analytics can help you quickly determine the velocity of a given group. It points to bottlenecks in the development process, enabling management to uncover, triage, and identify the root cause of slowdowns in the software development life cycle.

For information on how to contribute to the development of Value Stream Analytics, see our contributor documentation.

Group-level Value Stream Analytics is available via Group > Analytics > Value Stream.

Project-level Value Stream Analytics is also available.

Default stages

The stages tracked by Value Stream Analytics by default represent the GitLab flow. These stages can be customized in Group Level Value Stream Analytics.

  • Issue (Tracker)
    • Time to schedule an issue (by milestone or by adding it to an issue board)
  • Plan (Board)
    • Time to first commit
  • Code (IDE)
    • Time to create a merge request
  • Test (CI)
    • Time it takes GitLab CI/CD to test your code
  • Review (Merge Request/MR)
    • Time spent on code review
  • Staging (Continuous Deployment)
    • Time between merging and deploying to production

Filter the analytics data

Introduced in GitLab 13.3

GitLab provides the ability to filter analytics based on the following parameters:

  • Milestones (Group level)
  • Labels (Group level)
  • Author
  • Assignees

To filter results:

  1. Select a group.
  2. Click on the filter bar.
  3. Select a parameter to filter by.
  4. Select a value from the autocompleted results, or type to refine the results.

Value stream analytics filter bar

Date ranges

Introduced in GitLab 12.4.

GitLab provides the ability to filter analytics based on a date range. To filter results:

  1. Select a group.
  2. Optionally select a project.
  3. Select a date range using the available date pickers.

How Time metrics are measured

The “Time” metrics near the top of the page are measured as follows:

  • Lead time: median time from issue created to issue closed.
  • Cycle time: median time from first commit to issue closed. (You can associate a commit with an issue by crosslinking in the commit message.)

Value stream analytics time metrics

How the stages are measured

Value Stream Analytics measures each stage from its start event to its stop event. For example, a stage might start when one label is added to an issue, and end when another label is added. Value Stream Analytics excludes work in progress, meaning it ignores any items that have not reached the stop event.

Each stage of Value Stream Analytics is further described in the table below.

Stage Description
Issue Measures the median time between creating an issue and taking action to solve it, by either labeling it or adding it to a milestone, whatever comes first. The label will be tracked only if it already has an Issue Board list created for it.
Plan Measures the median time between the action you took for the previous stage, and pushing the first commit to the branch. The very first commit of the branch is the one that triggers the separation between Plan and Code, and at least one of the commits in the branch needs to contain the related issue number (e.g., #42). If none of the commits in the branch mention the related issue number, it is not considered to the measurement time of the stage.
Code Measures the median time between pushing a first commit (previous stage) and creating a merge request (MR) related to that commit. The key to keep the process tracked is to include the issue closing pattern to the description of the merge request (for example, Closes #xxx, where xxx is the number of the issue related to this merge request). If the closing pattern is not present, then the calculation takes the creation time of the first commit in the merge request as the start time.
Test Measures the median time to run the entire pipeline for that project. It’s related to the time GitLab CI/CD takes to run every job for the commits pushed to that merge request defined in the previous stage. It is basically the start->finish time for all pipelines.
Review Measures the median time taken to review the merge request that has a closing issue pattern, between its creation and until it’s merged.
Staging Measures the median time between merging the merge request with a closing issue pattern until the very first deployment to a production environment. If there isn’t a production environment, this is not tracked.

How this works, behind the scenes:

  1. Issues and merge requests are grouped together in pairs, such that for each <issue, merge request> pair, the merge request has the issue closing pattern for the corresponding issue. All other issues and merge requests are not considered.
  2. Then the <issue, merge request> pairs are filtered out by last XX days (specified by the UI - default is 90 days). So it prohibits these pairs from being considered.
  3. For the remaining <issue, merge request> pairs, we check the information that we need for the stages, like issue creation date, merge request merge time, etc.

To sum up, anything that doesn’t follow GitLab flow will not be tracked and the Value Stream Analytics dashboard will not present any data for:

  • Merge requests that do not close an issue.
  • Issues not labeled with a label present in the Issue Board or for issues not assigned a milestone.
  • Staging stage, if the project has no production environment.

How the production environment is identified

Value Stream Analytics identifies production environments by looking for project environments with a name matching any of these patterns:

  • prod or prod/*
  • production or production/*

These patterns are not case-sensitive.

You can change the name of a project environment in your GitLab CI/CD configuration.

Example workflow

Below is a simple fictional workflow of a single cycle that happens in a single day through all noted stages. Note that if a stage does not include a start and a stop time, its data is not included in the median time. It is assumed that milestones are created and a CI for testing and setting environments is configured. a start and a stop mark, it is not measured and hence not calculated in the median time. It is assumed that milestones are created and CI for testing and setting environments is configured.

  1. Issue is created at 09:00 (start of Issue stage).
  2. Issue is added to a milestone at 11:00 (stop of Issue stage / start of Plan stage).
  3. Start working on the issue, create a branch locally and make one commit at 12:00.
  4. Make a second commit to the branch which mentions the issue number at 12.30 (stop of Plan stage / start of Code stage).
  5. Push branch and create a merge request that contains the issue closing pattern in its description at 14:00 (stop of Code stage / start of Test and Review stages).
  6. The CI starts running your scripts defined in .gitlab-ci.yml and takes 5min (stop of Test stage).
  7. Review merge request, ensure that everything is OK and merge the merge request at 19:00. (stop of Review stage / start of Staging stage).
  8. Now that the merge request is merged, a deployment to the production environment starts and finishes at 19:30 (stop of Staging stage).

From the above example you can conclude the time it took each stage to complete as long as their total time:

  • Issue: 2h (11:00 - 09:00)
  • Plan: 1h (12:00 - 11:00)
  • Code: 2h (14:00 - 12:00)
  • Test: 5min
  • Review: 5h (19:00 - 14:00)
  • Staging: 30min (19:30 - 19:00)

A few notes:

  • In the above example we demonstrated that it doesn’t matter if your first commit doesn’t mention the issue number, you can do this later in any commit of the branch you are working on.
  • You can see that the Test stage is not calculated to the overall time of the cycle since it is included in the Review process (every MR should be tested).
  • The example above was just one cycle of the seven stages. Add multiple cycles, calculate their median time and the result is what the dashboard of Value Stream Analytics is showing.

Customizable Stages

Introduced in GitLab 12.9.

The default stages are designed to work straight out of the box, but they might not be suitable for all teams. Different teams use different approaches to building software, so some teams might want to customize their Value Stream Analytics.

GitLab allows users to create multiple value streams, hide default stages and create custom stages that align better to their development workflow.

Stage path

Version history

Value stream path navigation

Stages are visually depicted as a horizontal process flow. Selecting a stage updates the content below the value stream.

The stage time is displayed next to the name of each stage, in the following format:

Symbol Description
m Minutes
h Hours
d Days
w Weeks
M Months

Hovering over a stage item displays a popover with the following information:

  • Start event description for the given stage
  • End event description

Horizontal path navigation is enabled by default. If you have a self-managed instance, an administrator can open a Rails console and disable it with the following command:


Adding a stage

In the following example we’re creating a new stage that measures and tracks issues from creation time until they are closed.

  1. Navigate to your group’s Analytics > Value Stream.
  2. Click the Add a stage button.
  3. Fill in the new stage form:
    • Name: Issue start to finish.
    • Start event: Issue created.
    • End event: Issue closed.
  4. Click the Add stage button.

New Value Stream Analytics Stage

The new stage is persisted and it will always show up on the Value Stream Analytics page for your group.

If you want to alter or delete the stage, you can easily do that for customized stages by:

  1. Hovering over the stage.
  2. Clicking the vertical ellipsis () button that appears.

Value Stream Analytics Stages

Creating a custom stage requires specifying two events:

  • A start.
  • An end.

Be careful to choose a start event that occurs before your end event. For example, consider a stage that:

  • Started when an issue is added to a board.
  • Ended when the issue is created.

This stage would not work because the end event has already happened when the start event occurs. To prevent such invalid stages, the UI prohibits incompatible start and end events. After you select the start event, the stop event dropdown will only list the compatible events.

Re-ordering stages

Introduced in GitLab 12.10.

Once a custom stage has been added, you can “drag and drop” stages to rearrange their order. These changes are automatically saved to the system.

Label based stages

The pre-defined start and end events can cover many use cases involving both issues and merge requests.

For supporting more complex workflows, use stages based on group labels. These events are based on labels being added or removed. In particular, scoped labels are useful for complex workflows.

In this example, we’d like to measure more accurate code review times. The workflow is the following:

  • When the code review starts, the reviewer adds workflow::code_review_start label to the merge request.
  • When the code review is finished, the reviewer adds workflow::code_review_complete label to the merge request.

Creating a new stage called “Code Review”:

New Label Based Value Stream Analytics Stage

Hiding unused stages

Sometimes certain default stages are not relevant to a team. In this case, you can easily hide stages so they no longer appear in the list. To hide stages:

  1. Add a custom stage to activate customizability.
  2. Hover over the default stage you want to hide.
  3. Click the vertical ellipsis () button that appears and select Hide stage.

To recover a default stage that was previously hidden:

  1. Click Add a stage button.
  2. In the top right corner open the Recover hidden stage dropdown.
  3. Select a stage.

Creating a value stream

Introduced in GitLab 13.3

A default value stream is readily available for each group. You can create additional value streams based on the different areas of work that you would like to measure.

Once created, a new value stream includes the seven stages that follow GitLab workflow best practices. You can customize this flow by adding, hiding or re-ordering stages.

To create a value stream:

  1. Navigate to your group’s Analytics > Value Stream.
  2. Click the Value stream dropdown and select Create new Value Stream
  3. Fill in a name for the new Value Stream
  4. Click the Create Value Stream button.

New value stream

Creating a value stream with stages

Version history
cautionThis feature might not be available to you. Check the version history note above for details.

You can create value streams with stages, starting with a default or a blank template. You can add stages as desired.

To create a value stream with stages:

  1. Navigate to your group’s Analytics > Value Stream.
  2. Find and select the Value Stream dropdown. Select Create new Value Stream.
  3. Select either Create from default template or Create from no template.
    • Default stages in the value stream can be hidden or re-ordered Default stage actions
    • New stages can be added by clicking the ‘Add another stage’ button
    • The name, start and end events for the stage can be selected Custom stage actions
  4. Select the Create Value Stream button to save the value stream.

Extended create value stream form

Deleting a value stream

Introduced in GitLab 13.4.

To delete a custom value stream:

  1. Navigate to your group’s Analytics > Value Stream.
  2. Click the Value stream dropdown and select the value stream you would like to delete.
  3. Click the Delete (name of value stream).
  4. Click the Delete button to confirm.

Delete value stream

Days to completion chart

Version history

This chart visually depicts the total number of days it takes for cycles to be completed. (Totals are being replaced with averages in this issue.)

This chart uses the global page filters for displaying data based on the selected group, projects, and time frame. In addition, specific stages can be selected from within the chart itself.

The chart data is limited to the last 500 items.

Disabling chart

This chart is enabled by default. If you have a self-managed instance, an administrator can open a Rails console and disable it with the following command:


Type of work - Tasks by type chart

This chart shows a cumulative count of issues and merge requests per day.

This chart uses the global page filters for displaying data based on the selected group, projects, and time frame. The chart defaults to showing counts for issues but can be toggled to show data for merge requests and further refined for specific group-level labels.

By default the top group-level labels (max. 10) are pre-selected, with the ability to select up to a total of 15 labels.


To access Group-level Value Stream Analytics, users must have Reporter access or above.

You can read more about permissions in general.

More resources

Learn more about Value Stream Analytics in the following resources: