Jira Metric
Issue Tracking
Lead Time = Resolution Date − Creation Date
Lead Time measures the total elapsed time from when a Jira issue is created to when it is resolved. Unlike cycle time, lead time includes the time an issue spends waiting in the backlog before work begins, providing a customer-centric view of delivery speed.
JiraIssue TrackingLead Time
Lead Time measures the total elapsed time from when a Jira issue is created to when it is resolved. Unlike cycle time, lead time includes the time an issue spends waiting in the backlog before work begins, providing a customer-centric view of delivery speed.
How to calculate lead time
Why lead time matters for Jira users
Lead time represents the customer's experience of delivery speed. While teams may focus on cycle time, customers and stakeholders care about how long it takes from requesting something to receiving it. Reducing lead time improves responsiveness and customer satisfaction.
For Jira teams, lead time analysis reveals the full delivery pipeline, including backlog wait. Often, the majority of lead time is spent waiting rather than working, highlighting opportunities to improve prioritisation and reduce batch sizes.
Understand and act on lead time with KPI Tree
KPI Tree calculates lead time from Jira issue lifecycle data in your warehouse. Place this above cycle time in your flow metrics tree to show the full customer-facing delivery timeline.
Assign RACI ownership to product managers for lead time management. Set alerts when lead time exceeds customer expectations or service level agreements.
Get started with your Jira data
MCPPull metrics from Jira directly through the Model Context Protocol.
Connect your existing warehouse where Jira 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 Jira metrics
Cycle Time
Issue TrackingMetric Definition
Cycle Time = Done Date − In Progress Date
Cycle Time measures the elapsed time from when work actively begins on a Jira issue (typically moving to "In Progress") to when it is marked done. It captures the actual working duration, excluding backlog waiting time, and is a key indicator of process efficiency.
Flow Efficiency
Issue TrackingMetric Definition
Flow Efficiency = (Active Work Time / Total Cycle Time) × 100
Flow Efficiency measures the ratio of active work time to total cycle time for Jira issues. It reveals what percentage of an issue's lifecycle is spent in value-adding states versus waiting states such as review queues, approvals, or blocked status.
Blocked Time Percentage
Issue TrackingMetric Definition
Blocked Time Percentage = (Time in Blocked State / Total Cycle Time) × 100
Blocked Time Percentage calculates the proportion of an issue's total cycle time spent in a blocked or impeded state in Jira. It quantifies how much delivery time is consumed by waiting rather than active work.
Backlog Health Analysis
Issue TrackingMetric Definition
Backlog Health Analysis evaluates the overall quality and manageability of a Jira backlog. It considers factors such as issue age distribution, prioritisation consistency, estimation coverage, and the ratio of groomed to ungroomed items.
All Jira metrics
Backlog Health AnalysisBlocked Time PercentageCode Review Cycle TimeComponent Quality TrendsCross-Team Dependency AnalysisCycle TimeDefect DensityEpic Progress TrackingEscalation Pattern AnalysisFlow EfficiencyIssue Age DistributionIssue Resolution RatePriority Distribution AnalysisRelease Burnup AnalysisSprint Burndown AnalysisSprint Commitment AccuracySprint Goal Achievement RateSprint VelocityStory Point Estimation AccuracyTeam Capacity UtilisationTeam Collaboration IndexTechnical Debt RatioUser Productivity AnalysisVersion Release Success RateWorklog AccuracyEmpower your team to understand and act on Jira data
Map what drives your metrics, measure progress at any grain, prove what works statistically, and deliver personalised action plans to every team member.
