See where work waits before it ever reaches code
PR cycle time shows where code waits. Issue Lead Time shows where work waits before and around the code - from the moment an issue is created to the moment its PR merges. Connect Jira or Linear and watch the full delivery path, status by status.
Your delivery delays live outside the pull request
Engineering leaders measure code review and merge times closely, then wonder why features still take weeks to ship. The real delay often sits earlier: issues that age in the backlog, tickets parked in review, work stuck and blocked with no owner. Without visibility into the issue lifecycle, you are tuning the last mile while the first mile quietly eats your roadmap.
One view of the full issue-to-merge path
Issue Lead Time reads the status changelog from Jira or Linear and reconstructs how long each issue spends in every workflow state. It pairs that with the linked pull request to give you a single, end-to-end picture - backlog dwell, planning, coding, waiting, review, and merge.
Connect Jira or Linear
A standard OAuth connection pulls issue history and status changelogs into CodePulse. No agents, no scripts. Setup takes minutes, and the data populates as your trackers sync.
Measure end-to-end lead time
See median, average, and P90 lead time from issue created to PR merged, plus backlog dwell time and time to first commit. These are lead times for the whole delivery path, not just the code review window.
Break down time in every status
Status aging shows how long work sits in each workflow state - backlog, in progress, blocked, and the rest - using real transition timestamps. The longest-running statuses surface first.
Trace bottlenecks to repos and teams
Lead time breaks down by repository and by team, and backlog dwell drivers highlight where planning time piles up. You fix the workflow, not the people - this is a system view, not a scorecard.
Key Metrics You Will Track
Issue-to-Merge Lead Time
Median, average, and P90 time from issue creation to PR merge - the true end-to-end delivery clock
Backlog Dwell Time
How long issues sit after creation before any work or pull request begins
Time in Status
Average, median, and P90 time spent in each Jira or Linear workflow state, built from status change history
Bottleneck by Repo and Team
Where issue-to-merge time is longest across repositories and teams, so you target the right part of the system
Related Features
Break down cycle time into coding, waiting, review, and merge phases.
Connect Jira, Linear, and Azure DevOps so issue context enriches your GitHub-native analytics, with OAuth setup in minutes.
Predict delivery timelines based on historical velocity trends.
See Issue Lead Time in Action
Connect your GitHub account and get insights in under 5 minutes. Free forever for small teams.