> ## Documentation Index > Fetch the complete documentation index at: https://docs.heygarth.ai/llms.txt > Use this file to discover all available pages before exploring further. # Pr metrics ## PR Metrics Dashboard ### Overview The PR Metrics Dashboard provides insights into Pull Request (PR) activities, collaboration patterns, repository contributions, and code review efficiency across engineering teams. The dashboard enables engineering teams and leadership to analyze PR lifecycle activities and identify opportunities to improve collaboration, code quality, and delivery efficiency. ## Key Performance Indicators ### What is it? A summary section displaying high-level PR workflow and code contribution metrics. ### Why is it important? Provides a quick overview of development activity, code review throughput, and merge efficiency without requiring detailed chart analysis. ### Where does it exist? Top section of the PR Metrics dashboard. ### Metrics Included #### PRs Raised Total number of pull requests created within the selected time period. #### PRs Merged Total number of successfully merged pull requests. #### Lines Added Total number of lines of code added through pull requests. #### Lines Removed Total number of lines of code removed through pull requests. #### Average PR Merge Time Average time taken for pull requests to be merged after creation. ## PR Activity Trend ### What is it? A time series visualization showing PR activity and merge performance trends over time. ### Why is it important? Helps teams monitor development velocity, merge consistency, and workflow efficiency. ### Where does it exist? Middle section of the dashboard under the KPI cards. ### Metrics Included * PRs Raised * PRs Merged * Average Merge Time ### Use Cases * Monitor engineering productivity * Identify delays in PR processing * Track merge performance trends * Analyze release cycle activity ## PRs by Repositories ### What is it? A repository-wise breakdown of pull request activity. ### Why is it important? Helps identify repositories with the highest development activity and contribution volume. ### Where does it exist? Upper-middle section of the dashboard. ### Use Cases * Track repository contribution distribution * Identify highly active repositories * Monitor engineering workload across projects ## PRs Raised by Team Member ### What is it? A chart displaying the number of pull requests raised by individual contributors. ### Why is it important? Provides visibility into contributor activity and development participation across the team. ### Where does it exist? Lower-middle section of the dashboard. ### Use Cases * Measure contributor engagement * Track development participation * Analyze team contribution patterns ## Top PR Approvers ### What is it? A ranking chart showing users who approved the highest number of pull requests. ### Why is it important? Helps measure code review participation and reviewer engagement across engineering teams. ### Where does it exist? Upper section of the dashboard. ### Use Cases * Identify active reviewers * Monitor code review participation * Track review ownership distribution ## Top PR Mergers ### What is it? A chart displaying users responsible for merging the highest number of pull requests. ### Why is it important? Provides visibility into merge ownership and release coordination responsibilities. ### Where does it exist? Upper-middle section of the dashboard below Top PR Approvers. ### Use Cases * Track merge management activities * Identify release coordinators * Monitor repository maintenance responsibilities ## Top PR Commenters ### What is it? A ranking chart showing users with the highest PR comment activity. ### Why is it important? Measures collaboration, review engagement, and participation in code quality discussions. ### Where does it exist? Bottom section of the dashboard. ### Use Cases * Track collaboration activity * Measure review discussion engagement * Identify highly active contributors in PR reviews ## Controls and Filters ### What is it? Interactive controls used to customize dashboard data and reporting views. ### Why is it important? Allows users to analyze PR metrics across different time periods and reporting granularities. ### Where does it exist? Top section of the dashboard. ### Features #### Date Range Filter Allows users to select a custom time period for analysis. #### Time Granularity Toggle Supports Daily, Weekly, and Monthly trend analysis. #### PR Metrics / Team Metrics / ROI Tabs Allows switching between different engineering analytics views. ## Actions ### Executive Summary #### What is it? A high-level summarized view of PR workflow performance and engineering collaboration insights. #### Why is it important? Provides leadership and stakeholders with quick insights into engineering activity and review efficiency. ### Export Report #### What is it? An option to export dashboard data and reports. #### Why is it important? Enables offline reporting, data sharing, and external analysis. ## Key Use Cases ### Development Activity Monitoring Track overall pull request creation and merge activity. ### Code Review Participation Measure reviewer engagement and collaboration across teams. ### Merge Efficiency Analysis Monitor PR merge timelines and workflow bottlenecks. ### Repository Contribution Tracking Analyze contribution patterns across repositories. ### Engineering Productivity Insights Measure development throughput and code contribution trends. # Team Metrics ## Team Metrics Dashboard ### Overview The Team Metrics tab provides contributor-level insights into pull request activity, code contribution patterns, review participation, and developer engagement across engineering teams. The dashboard focuses on individual developer activity and team-wide contribution trends to support workload analysis, performance tracking, and engineering process optimization. ## Key Performance Indicators ### What is it? A summary section displaying high-level contributor and PR activity metrics. ### Why is it important? Provides a quick overview of team participation, code contribution volume, and review activity. ### Where does it exist? Top section of the Team Metrics dashboard. ### Metrics Included #### PRs Raised by Team Total number of pull requests created by team members during the selected time period. #### Lines Added by Team Total number of lines of code added by contributors through pull requests. #### Review Comments by Developers Total number of review comments made by developers during PR reviews. #### Line Impact Distribution Tracks the balance between code additions and deletions across team contributions. ## PRs Raised by Team Member ### What is it? A contributor-wise chart showing the number of pull requests raised by each team member. ### Why is it important? Helps identify active contributors and measure development participation across the team. ### Use Cases * Track contributor activity * Analyze development workload distribution * Identify highly active developers * Measure team participation ## Lines Added by Team Member ### What is it? A chart displaying the total number of lines of code added by each contributor. ### Why is it important? Provides visibility into code contribution volume across developers and teams. ### Use Cases * Measure contribution volume * Track development output * Analyze repository contribution distribution * Identify major code contributors ## PRs Raised by Main Team ### What is it? A comparison chart showing pull requests raised by the primary engineering team. ### Why is it important? Helps evaluate overall development activity from core engineering contributors. ### Use Cases * Track core team contribution levels * Measure primary engineering activity * Analyze workload concentration ## PRs Raised by Sub Teams ### What is it? A chart comparing pull request activity across sub-teams or secondary contributor groups. ### Why is it important? Provides visibility into development participation across different organizational units. ### Use Cases * Compare contribution levels across teams * Track team-level productivity * Identify imbalances in engineering workload ## PRs Raised Trends ### What is it? A time series chart displaying monthly PR creation trends. ### Why is it important? Helps monitor engineering activity growth, consistency, and release patterns over time. ### Use Cases * Track release activity trends * Identify productivity spikes or slowdowns * Monitor long-term development patterns ## Lines Added Trends ### What is it? A trend visualization showing code addition activity over time. ### Why is it important? Provides insight into development intensity and coding activity trends. ### Use Cases * Monitor coding activity over time * Track engineering throughput * Analyze release cycle contribution patterns ## Critical Review Comments Against Developers ### What is it? A contributor-wise chart displaying the number of critical review comments received by developers during pull request reviews. ### Why is it important? Helps identify quality concerns, review feedback concentration, and areas requiring improvement. ### Use Cases * Track code review quality feedback * Identify recurring review concerns * Improve coding standards and best practices * Monitor developer review outcomes ## Developer Adoption Metrics ### What is it? A chart measuring developer participation and adoption of PR workflows and engineering processes. ### Why is it important? Helps assess engineering engagement and process adoption across contributors. ### Use Cases * Measure engineering participation * Track workflow adoption * Monitor contributor engagement levels ## Last Time PRs Raised by Team Members (In Days) ### What is it? A chart showing the number of days since each team member last raised a pull request. ### Why is it important? Provides visibility into contributor activity recency and identifies inactive contributors. ### Use Cases * Identify inactive contributors * Monitor contribution consistency * Track developer engagement over time ## Controls and Filters ### Features #### Date Range Filter Allows users to analyze data for a selected time period. #### Project Filter Filters metrics based on selected engineering projects. #### Repository Filter Filters contribution data for a selected repository. #### Developer Name Filter Allows contributor-specific analysis. #### Daily / Weekly / Monthly Toggle Supports multiple time granularities for trend analysis. ## Actions ### Executive Summary Provides quick engineering productivity insights for stakeholders and managers. ### Export Report Supports reporting, sharing, and offline analysis. ## Key Use Cases ### Contributor Activity Tracking Monitor individual developer participation and PR activity. ### Team Productivity Analysis Measure engineering throughput and contribution levels. ### Review Quality Monitoring Track review comments and critical feedback trends. ### Contribution Distribution Analysis Understand workload allocation across developers and teams. ### Engineering Engagement Insights Measure adoption and consistency of engineering workflows. # ROI ## ROI Dashboard ### Overview The ROI tab provides financial and productivity impact analysis for Pull Request workflows and engineering activities. The dashboard converts engineering workflow metrics into time-saving and cost-saving indicators to help leadership understand the business impact of development activities. ## Tenant ROI Configuration ### What is it? A configuration-driven summary section displaying estimated productivity gains, time savings, and financial impact generated from PR workflow activities. ### Why is it important? Helps quantify the business value of engineering processes and demonstrates the return on investment generated through efficient pull request management and collaboration practices. ## Metrics Included ### Average PRs Per Month Displays the average number of pull requests created per month across the organization or selected engineering scope. ### Total Time Saved Per Month Represents the estimated amount of engineering time saved every month through optimized PR workflows and review efficiency improvements. ### Total Time Saved Per Annual Displays the estimated annualized engineering time savings generated through PR process optimization. ### Total Cost Saved Per Month Displays the estimated monthly financial savings generated through reduced engineering effort and improved workflow efficiency. ### Total Cost Saved Per Year Represents the projected annual cost savings generated through optimized PR processes and engineering efficiency gains. ## Controls and Navigation ### Features #### PR Metrics Tab Displays overall pull request activity and workflow analytics. #### Team Metrics Tab Displays contributor-level and team-based engineering metrics. #### ROI Tab Displays financial and productivity impact analysis related to PR workflows. #### Refresh Option Allows users to reload and refresh dashboard data. ## Key Use Cases ### Productivity Impact Analysis Measure engineering time savings generated through optimized workflows. ### Financial Impact Measurement Track estimated monthly and annual cost savings. ### Engineering Efficiency Evaluation Quantify improvements in PR handling and review processes. ### Leadership Reporting Provide management with measurable business value indicators. ### ROI Benchmarking Evaluate the effectiveness of engineering process improvements over time.