Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,763
    • Issues 44,763
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,330
    • Merge requests 1,330
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #340150
Closed
Open
Issue created Sep 05, 2021 by Dan Jensen@djensenContributor

[VSA] License check for Lead Time For Changes (DORA)

Problem to solve

We plan to display the DORA Lead Time For Changes metric in VSA. Before that, we must ensure the data is subject to the correct license check.

Proposal

Add a license check in VSA that will allow DORA Lead Time For Changes to be displayed for GitLab Ultimate, but not for GitLab Premium or GitLab Free. In other words, only expose the DORA metric if the license check is successful. (This is very similar to the license check for DORA Deployment Frequency.)

Edited Sep 16, 2021 by Dan Jensen
Assignee
Assign to
Time tracking