Find out how much of your cycle time is spent in draft

Cycle time is an aggregate metric, and alone it doesn’t describe where things slow down. Now you can look at each pull request stage and analyze outliers in each — whether it’s review time, merge time, in progress time or time as a draft.

Draft time shows how much of a pull request’s cycle time it spent in draft status. Because a pull request can be a draft at any stage, draft time overlaps the other components instead of adding to the total, so your cycle time number stays the same. Pull requests that move in and out of draft several times have all of those stints counted.

This is useful for every team, but especially if your engineers open pull requests early and leave them in draft before picking the work up. Now you can see how much of the cycle time that accounts for.

You can view draft time on an individual pull request, as an aggregate number next to the other components, and as a distribution of pull requests by total time in draft. It’s also available as a pull request property in explore.

Go to metrics → code metrics → cycle time and click any pull request on the chart to see it in the sidebar.

More updates:

• Your saved views in explore are now private by default. All of your reports and explorations stay private until you’re ready to share them — with one colleague, a few of them, or the whole organization. It’s handy for when a report is still taking shape, or when it’s only relevant to your immediate team. We also removed the horizontal scrolling in the view tabs and added pinning for the views you come back to most.
• The AI in explore now uses conversational chat. Ask a question, create a new report, or refine one you already have using plain language.
• Follow AI spend in the work log. Select AI spend in the activity legend at the bottom of the work log to add a badge to each day, showing which AI tools were used and the token value for that day.