Jira Metric
Issue Tracking
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.
JiraIssue TrackingCode Review Cycle Time
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.
How to calculate code review cycle time
Why code review cycle time matters for Jira users
Code review is often the largest bottleneck in software delivery pipelines. Long review times increase context-switching costs for both authors and reviewers, and delay the delivery of completed features to users.
For Jira teams, tracking code review cycle time reveals whether review processes are keeping pace with development throughput. It helps identify teams or individuals who may need additional reviewers, clearer review standards, or better tooling to reduce review turnaround.
Understand and act on code review cycle time with KPI Tree
KPI Tree extracts review stage duration from Jira workflow transition data in your warehouse. Place this metric in your development flow tree between coding and deployment stages.
Assign RACI ownership to tech leads for review turnaround standards. Set alerts when review cycle time exceeds your team's service level agreement.
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.
Team Capacity Utilisation
Issue TrackingMetric Definition
Capacity Utilisation = (Allocated Story Points / Available Capacity) × 100
Team Capacity Utilisation measures the proportion of available team capacity that is actively allocated to Jira issues. It compares assigned workload against available capacity, accounting for team member availability, leave, and non-project commitments.
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 PercentageComponent 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.
