GitHub Metric
Engineering
Issue Resolution Time = Issue Closed Timestamp − Issue Created Timestamp
Issue Resolution Time measures the elapsed time from when a GitHub issue is opened to when it is closed. It reflects team responsiveness, prioritisation effectiveness, and overall execution speed. Segmenting by label (bug, feature, chore) provides more actionable insights.
GitHubEngineeringIssue Resolution Time
Issue Resolution Time measures the elapsed time from when a GitHub issue is opened to when it is closed. It reflects team responsiveness, prioritisation effectiveness, and overall execution speed. Segmenting by label (bug, feature, chore) provides more actionable insights.
How to calculate issue resolution time
Why issue resolution time matters for GitHub users
Slow issue resolution frustrates reporters - whether they are customers, teammates, or open-source contributors - and signals an overwhelmed or poorly prioritised team. Aging issues also become stale, requiring re-investigation when finally addressed.
Tracking resolution time in GitHub by issue type helps teams set realistic SLAs and allocate capacity appropriately. It also provides evidence for staffing requests when resolution times consistently exceed targets.
Understand and act on issue resolution time with KPI Tree
Sync GitHub issue lifecycle data into your warehouse and model resolution time in KPI Tree, segmented by label and priority. Place it in a product quality tree alongside bug fix rate and customer satisfaction.
Assign RACI ownership to product or engineering leads and configure alerts when resolution time exceeds SLA thresholds for critical issue types.
Get started with your GitHub data
MCPPull metrics from GitHub directly through the Model Context Protocol.
Connect your existing warehouse where GitHub data already lands.
Our professional services team can build you turn-key AI foundations in a matter of weeks. Data warehouse on Snowflake/BigQuery, ELT with Fivetran, all modelled in dbt with a semantic layer.
Related GitHub metrics
Bug Fix Rate
EngineeringMetric Definition
Bug Fix Rate = Bugs Closed in Period / Total Open Bugs at Start of Period × 100
Bug Fix Rate measures the proportion of bug-labelled issues closed within a given period relative to the total number of open bugs. It reflects a team's capacity and prioritisation of quality work. A consistently low rate may signal under-investment in reliability.
Sprint Velocity Tracking
EngineeringMetric Definition
Sprint Velocity = Sum of Story Points (or Issue Count) Completed in Sprint
Sprint Velocity Tracking measures the amount of work - typically in story points or issue count - completed during each sprint or iteration, as tracked through GitHub Projects. It provides a baseline for capacity planning and helps teams set realistic commitments for upcoming sprints.
Security Alert Resolution Time
EngineeringMetric Definition
Resolution Time = Alert Resolved Timestamp − Alert Created Timestamp
Security Alert Resolution Time measures the elapsed time from when a security alert (Dependabot, code scanning, or secret scanning) is opened to when it is resolved or dismissed in GitHub. It quantifies the organisation's responsiveness to known vulnerabilities and the effectiveness of its security remediation process.
Feature Development Cycle Time
EngineeringMetric Definition
Cycle Time = Deployment Timestamp − First Feature Commit Timestamp
Feature Development Cycle Time measures the elapsed time from the first commit on a feature branch to successful deployment to production. It encompasses coding, review, testing, and release phases. Shorter cycle times enable faster user feedback and more responsive product development.
Explore issue resolution time across integrations
All GitHub metrics
Branch Lifecycle AnalysisBug Fix RateCode Churn RateCode Coverage TrendCode Quality Trend AnalysisCode Review Quality ScoreCode Review VelocityCommit FrequencyDeployment FrequencyDeveloper Contribution PatternsDeveloper Productivity ScoreDevOps Pipeline EfficiencyDiscussion Engagement RateFeature Development Cycle TimeLead Time for ChangesOpen Source Contribution AnalysisPull Request Approval RatePull Request Bottleneck AnalysisRelease VelocityRepository Health ScoreSecurity Alert Resolution TimeSecurity Vulnerability TrendsSprint Velocity TrackingTeam Collaboration IndexTechnical Debt AccumulationEmpower your team to understand and act on GitHub data
Map what drives your metrics, measure progress at any grain, prove what works statistically, and deliver personalised action plans to every team member.
