Icon header

Introducing GitLab Cycle Analytics

Real data, better decisions.

View Blog Post

What is GitLab Cycle Analytics?

Real data on your project

Estimates are often incorrect. Stop estimating. Cycle Analytics lets you know how long it takes your team to complete each stage in their workflow from idea to production.

Built for managers and teams

One shared view of the team's velocity. With insights into how long it takes the team to move from idea to production, you can pinpoint areas for improvement.

No setup required

Cycle Analytics is pre-configured and ready to track your workflow. It follows the GitLab Flow and records the median time it takes the team to complete each stage.

Cycle Analytics Overview

Cycle analytics view

Watch our webcast!

Hear more about Cycle Analytics and the other new features in GitLab 8.12
Watch on YouTube

Understanding GitLab Cycle Analytics

Cycle Analytics is available in GitLab.com, GitLab Community Edition, and GitLab Enterprise Edition.

Navigate to your Project's Pipelines > Cycle Analytics to access the dashboard.

[ stage 01 ]

Issue

How long until you start working on an issue?

This stage measures the time between creating an issue and taking action to solve it, by either assigning it to a milestone or moving it into a list on your Issue Board, whichever comes first.

Stage 1 illustration
[ stage 02 ]

Plan

How long until your first commit?

Stage 2 illustration

This stage measures the time between the action you took for the previous stage, and pushing the first commit to the repository.

GitLab tracks this using the issue closing pattern like closes #xxx, where xxx is the number of the issue related to this commit.

[ stage 03 ]

Code

How long until you create a merge request (MR)?

This stage measures the time between pushing a first commit (previous stage) and creating a merge request related to that commit.

GitLab tracks this using the issue closing pattern like closes #xxx in the MR description, where xxx is the number of the issue related to this merge request.

Stage 3 illustration
[ stage 04 ]

Test

How much time does it take GitLab CI to test your code?

Stage 4 illustration

This stage measures the time to run the entire pipeline for that project.

It's related to the time GitLab CI takes to run every job for the commits pushed to that MR defined in the previous stage.

[ stage 05 ]

Review

How much time do you spend on code review?

This stage measures the time taken to review the MR, from the moment it's created until the moment it's merged.

Stage 5 illustration
[ stage 06 ]

Staging

We're ready to go now! What's the length of time between merging and deploying to production?

Stage 6 illustration

This stage measures the time spent in staging, from merging the MR until the app is deployed to production.

It's tracked by the environment set to production in your GitLab CI configuration.

[ stage 07 ]

Production

Total lifecycle time: how fast is my team?

This is the measure of the time taken to run entire process, from creating an issue to deploying the code to production.

In fact, this is the time your team takes to go from idea to production!

Read through the Cycle Analytics documentation to learn more.

Stage 7 illustration

Try GitLab Enterprise Edition risk-free for 30 days.

No credit card required. Have questions? Contact us.

Get Your Free Trial Today

Try GitLab Enterprise Edition risk-free for 30 days.

No credit card required. Have questions? Contact us.