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,329
    • Merge requests 1,329
  • 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
  • #229389
Closed
Open
Issue created Jul 15, 2020 by Jeremy Watson (ex-GitLab)@jeremy-glContributor

[MR Analytics] Add MTTM container (FE)

Problem

Mean time to merge (MTTM) will be a metric our users will want to actively track and manage.

Proposal

image

  • For the time period and filtered criteria, show the mean time to merge (the average amount of time between MR opened and MR merged).

Note: This is the frontend implementation issue. The backend issue is here: #246820 (closed).

Note 2: On the screenshot we see the possibility to choose the time period, but that is not yet implemented, the default time is past 12 months.

Edited Sep 17, 2020 by Magdalena Frankiewicz
Assignee
Assign to
Time tracking