Jira Metric
Issue Tracking
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.
JiraIssue TrackingFlow Efficiency
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.
How to calculate flow efficiency
Why flow efficiency matters for Jira users
Most organisations are shocked to discover that their flow efficiency is below 15%, meaning issues spend over 85% of their time waiting. This metric makes the invisible waste of waiting visible and provides the motivation to streamline handoffs and reduce queues.
For Jira teams, flow efficiency is the ultimate process health indicator. Improving it even marginally can dramatically reduce cycle time without requiring teams to work harder, only smarter by removing unnecessary waiting states.
Understand and act on flow efficiency with KPI Tree
KPI Tree calculates flow efficiency from Jira workflow state duration data in your warehouse. Place this at the top of your process improvement tree, with blocked time and code review cycle time as key inputs.
Assign RACI ownership to agile coaches or process improvement leads. Set improvement targets and alert when flow efficiency trends downward.
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.
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.
Code Review Cycle Time
Issue TrackingMetric Definition
Code Review Cycle Time = Review Completion Date − Review Start Date
Code Review Cycle Time measures the elapsed time between when a Jira issue enters a code review state and when it exits, either approved or requiring changes. It captures the efficiency of the review process as reflected in Jira workflow transitions.
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.
All Jira metrics
Backlog Health AnalysisBlocked Time PercentageCode Review Cycle TimeComponent Quality TrendsCross-Team Dependency AnalysisCycle TimeDefect DensityEpic Progress TrackingEscalation Pattern AnalysisIssue 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.
