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
  • #232651
You need to sign in or sign up before continuing.
Closed
Open
Issue created Jul 28, 2020 by Martin Wortschack@wortschi🔴Maintainer

[FE] Display data table of MRs in Merge Request Analytics

Problem

When viewing the MR Analytics page, I want to be able to view the individual MRs that are in the chart to better understand the underlying MRs that drove the trend.

Proposal

When viewing MR Analytics, show the individual merged MRs depicted in the throughput chart in a data table:

Throughput_table_+_chart_MVC

  • Limit to the first 100 records, sorted by id/created_at (per #229365 (comment 382190171))
  • Columns to show:
    • Date merged
    • Time to merge
    • Milestone
    • Comments
    • Commits
    • Approvals (number of approvals)
    • Pipelines (with a check if the MR passed CI when merged)
    • Line changes

Out of scope

  • Sorting by column will be implemented in a follow-up: #230562
  • Pagination will be implemented in a follow-up: #229842 (closed)
Edited Jul 28, 2020 by Martin Wortschack
Assignee
Assign to
Time tracking