Jira Metric
Issue Tracking
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.
JiraIssue TrackingBlocked Time Percentage
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.
How to calculate blocked time percentage
Why blocked time percentage matters for Jira users
Blocked time is pure waste in the delivery process. Every hour an issue sits blocked extends its cycle time without adding value. High blocked time percentages reveal systemic impediments such as approval bottlenecks, cross-team dependencies, or environment availability issues.
For Jira teams, tracking blocked time surfaces the root causes of delivery delays that are not visible in simple throughput metrics. It provides the evidence needed to justify investment in removing organisational impediments.
Understand and act on blocked time percentage with KPI Tree
KPI Tree calculates blocked time from Jira status transition data in your warehouse. Position this metric in your flow efficiency tree alongside cycle time and lead time.
Assign RACI ownership to scrum masters for impediment resolution. Set alerts when blocked time percentages exceed team targets, triggering immediate investigation.
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.
Lead Time
Issue TrackingMetric Definition
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.
Cross-Team Dependency Analysis
Issue TrackingMetric Definition
Cross-Team Dependency Analysis maps the network of issue links, blockers, and handoffs between different Jira projects and teams. It quantifies how often teams depend on each other and measures the impact of those dependencies on delivery timelines.
All Jira metrics
Backlog Health AnalysisCode Review Cycle TimeComponent Quality TrendsCross-Team Dependency AnalysisCycle TimeDefect DensityEpic Progress TrackingEscalation Pattern AnalysisFlow EfficiencyIssue Age DistributionIssue Resolution RateLead TimePriority 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.
