AI Impact analytics

DETAILS: Tier: Ultimate with GitLab Duo Enterprise - Start a trial Offering: GitLab.com, Self-managed

• Introduced in GitLab 16.11 with a flag named ai_impact_analytics_dashboard. Disabled by default.
• Generally available in GitLab 17.2. Feature flag ai_impact_analytics_dashboard removed.
• Changed to require GitLab Duo add-on in GitLab 17.6 and later.

AI Impact analytics displays software development lifecycle (SDLC) metrics for a project or group in the month-to-date and the past six months.

Use AI Impact analytics to:

• Measure the effectiveness and impact of AI on SDLC metrics.
• Visualize which metrics improved as a result of investments in AI.
• Track the progress of AI adoption.
• Compare the performance of teams that are using AI against teams that are not using AI.

For a click-through demo, see the AI Impact analytics product tour.

AI Impact metrics

AI Impact analytics displays key metrics and metric trends for a project or group.

Key metrics

• Code Suggestions: Unique users: Percentage of users that engage with Code Suggestions every month. It is calculated as the number of monthly unique Code Suggestions users divided by total monthly unique contributors. Only unique code contributors, meaning users with pushed events, are included in the calculation.
• Code Suggestions: Acceptance rate: Percentage of code suggestions provided by GitLab Duo that have been accepted by code contributors in the last 30 days.
• Duo Chat: Unique users: Percentage of users that engage with Duo Chat every month. It is calculated as the number of monthly unique Duo Chat users divided by the total GitLab Duo assigned users.

Metric trends

The Metric trends table displays metrics for the last six months, with monthly values, percentage changes in the past six months, and trend sparklines.

Lifecycle metrics

• Cycle time
• Lead time
• Deployment frequency
• Change failure rate
• Critical vulnerabilities over time

AI usage metrics

• Code Suggestions usage: Monthly user engagement with AI Code Suggestions.

  • The month-over-month comparison of the AI Usage unique users rate gives a more accurate indication of this metric, as it eliminates factors such as developer experience level and project type or complexity.
  • The baseline for the AI Usage trend is the total number of code contributors, not just users with GitLab Duo seats. This baseline gives a more accurate representation of AI usage by team members. To learn more about AI Impact analytics, see the blog post Developing GitLab Duo: AI Impact analytics dashboard measures the ROI of AI.
  • To analyze the performance of teams that use AI versus teams that don't, you can create a custom Value Streams Dashboard Scheduled Report based on the AI Impact view of projects and groups with and without GitLab Duo.

  NOTE: Usage rate for Code Suggestions is calculated with data starting from GitLab 16.11. For more information, see epic 12978.

View AI Impact analytics

Prerequisites:

• Code Suggestions must be enabled.
• ClickHouse for contribution analytics must be configured.

1. On the left sidebar, select Search or go to and find your project or group.
2. Select Analyze > Analytics Dashboards.
3. Select AI impact analytics.