Jira Metric
Issue Tracking
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.
Full guide: definition, formula, and benchmarksJiraIssue TrackingCycle Time
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.
How to calculate cycle time
Why cycle time matters for Jira users
Cycle time is the most actionable flow metric for engineering teams. Unlike lead time, which includes backlog wait, cycle time focuses on the work itself. Reducing cycle time means faster delivery, quicker feedback loops, and more responsive teams.
For Jira teams, cycle time analysis by issue type, priority, and team reveals where process improvements will yield the greatest delivery gains. It helps teams identify whether delays are caused by task size, blockers, or process inefficiencies.
Understand and act on cycle time with KPI Tree
KPI Tree calculates cycle time from Jira workflow transition data in your warehouse. Place this at the centre of your flow metrics tree, with blocked time and flow efficiency as supporting indicators.
Assign RACI ownership to delivery leads for cycle time targets. Set alerts when median cycle time exceeds your team's agreed service level expectations.
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
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.
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.
Sprint Velocity
Issue TrackingMetric Definition
Sprint Velocity = Total Story Points Completed per Sprint
Sprint Velocity measures the total story points or issue count completed by a team in each Jira sprint. It provides a rolling baseline of team capacity that is used for forecasting future delivery and calibrating sprint commitments.
Explore cycle time across integrations
All Jira metrics
Backlog Health AnalysisBlocked Time PercentageCode Review Cycle TimeComponent Quality TrendsCross-Team Dependency AnalysisDefect 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.
