How Do I Build a Metrics Dashboard?

Creating custom dashboards in LinearB allows you to build custom metrics reports focusing in on team, individual, or repo metrics. You can create as many new dashboards as you like. Dashboards can be kept private to your user account, or made public to your whole team.

How To Create A Dashboard

1. Click the icon in the top left of your Metrics page.
2. Name your dashboard.
3. Add a description. When you hover over the dashboard title, this description will be visible.
4. Filter by: You can focus a dashboard on a specific team, team member, or Git repository.
   1. Team(s): Select one or more teams. Read more about multiple team dashboards here: How to select multiple teams in a metrics report
   2. People: Dashboards can be created to review an individual team member.
      • Team member dashboards are useful for 1:1 meetings.
   3. Repository: Select any repository you've linked to LinearB
      • More repositories can be added by clicking on Company Settings > Git > Add Repositories
      • Repo dashboards are an excellent report for monitoring services.
5. Mark dashboards public or private. The lock icon allows you to keep a dashboard visible to only yourself, or to make public for other users in your account to access.
6. Add Metrics: click on the +Add metrics button, check the metrics you would like to display, click Save.

Customizing Your Dashboard

• Reorder your metrics widgets: All widgets can be dragged into any desired order.
• Select which team(s) to display: Use the teams dropdown to select up to 6 teams to display on your dashboard.
• Filter by Repo, Label, or Service: Instead of focusing on teams, you an also focus on specific repos, labels, or services.
• Duplicate dashboards: Quickly use template dashboard to build focused reports on specific teams or repositories. Copy any existing dashboard with your new changes using the Save As button.

Customize Your Widgets

• Change from Average to Percentile: Click on the dropdown on any widget to switch the displayed numbers from Average, to P75 (75th Percentile), or P50 (50th Percentile).
• Change graph color: Use the button to change the color of any chart.
• Change chart-type: Use the button to switch between line-charts and bar-charts.

Available Metrics:

Delivery Metrics

• Cycle Time
  • Measure the average time it takes for a branch to move from first commit to release.
• Coding Time
  • Time from first commit to pull request creation.
• Pickup Time
  • Time from pull request creation to review.
• Review Time
  • Time from review beginning to pull request merged
• Deploy Time
  • Time from pull request merge to release
• Time to approve
  • Time from review beginning to pull request first approval
• Time to merge
  • Time from pull request first approval to pull request merged

Quality Metrics

• PR Size
  • Size of pull request (total lines of code changed)
• Review Depth
  • Avg. number of comments per review
• New code
  • Ratio of new code
• Refactor
  • Ratio of legacy code changed (more than 21 days)
• Rework
  • Ratio of novice code changed (less than 21 days)
• PRs merged w/o review
  • Number of pull requests merged without any review

Throughput Metrics

• Code changes
  • Lines of code changed
• Commits
  • Number of commits
• PRs opened
  • Number of pull requests opened
• PRs merged
  • Number of pull requests merged
• Merge Frequency
  • Number of pull requests merged
• Reviews
  • Number of pull requests reviews
• Deploy frequency
  • Avg. of releases per day
• Done Branches
  • Number of branches moved to state merged or released

Balance Metrics

• Active days
  • Number of days with Git activity (commits, PRs, Reviews etc.)
• Active Branches
  • Number of branches in active state

Project Management Metrics

• MTTR
  • Mean time to restore
• CFR
  • Change failure rate