Code Cycle Time looks at all your completed Pull Requests (e.g. closed, merged, declined etc) within the specified time range and shows the average hours to complete, from when the PR was opened. Not only that but it provides full insight into the different stages that a PR goes through. They are defined as:

  1. Time to Review - From open to the first comment or review

  2. Time to Approve - From the previous stage to approved

  3. Time to Merge/Close - From the previous stage to merge/close

  4. Time to Deploy - From the previous stage to deployed (this will only appear if you integrate with our Pipeline API and push deployment data to Plandek)

As with all Plandek metrics, there are numerous powerful bespoke views that can be created using the Breakdown and Filters. Below is a selection of the options available:


The individual who created the PR. Useful to filter down to a specific individual or individuals across many repos.


Any individual who took action on the PR (not including the Author). Great way to see who are the goto team members for reviews etc.


The specific stage the PR has been through (as defined above in the article). Essential to understand where time is being spent on average across your completed PRs.


Allows you to see how Code Cycle Time compares across repos and if PRs in particular repos take longer than others.

Ticket Issue Type

Based on ticket reference linking, you can gain a unique perspective on this metric based on any Ticket related field you have configured. In this case, you would be able to understand code cycle time based on the related ticket being a Story or Bug etc.

Did this answer your question?