## Problem Throughput is [widely](http://blog.robbowley.net/2012/01/06/productivity-throughput-and-cycle-time/) [used](http://blog.plataformatec.com.br/2016/02/why-we-love-metrics-throughput-and-burnup-charts/) as a [measure](https://leankit.com/learn/kanban/lean-flow-metrics/) of [productivity](https://weblogs.asp.net/wallen/throughput-vs-velocity) in the software development industry. In fact, GitLab itself uses Throughput as one of its [primary development KPIs](https://about.gitlab.com/handbook/engineering/development/performance-indicators/#throughput), and is [auditing](https://gitlab.com/gitlab-com/www-gitlab-com/issues/6273), [refining](https://gitlab.com/gitlab-org/gitlab/issues/24786) and [possibly expanding](https://gitlab.com/gitlab-org/gitlab/issues/27810) its usage of Throughput. It seems there is clear demand for an interface that would help users understand Throughput in GitLab. ## Proposal Add a group-level "Merge Requests Analytics" page, accessible from the Analytics menu in the left-nav:  The first chart we'll prioritize on this page is Throughput (the total number of merge requests merged in a period). The data displayed in the chart can be specified using the filter bar.