Why cannot I see cycle time against developers even though they have commits?

We calculate the cycle time and related metrics only after a PR is merged. Once the PR is merged, based on the date of first commit till the time it took to get merged, we calculate the cycle time and similarly the coding, review, and merge times.

Hence, even though a developer has made commits against an open PR, unless that PR is merged we do not take it into consideration for cycle time calculation.

Why only merged PRs though?

1. Complete Lifecycle Analysis:

   • Metrics like cycle time, coding time, review time, and merge time represent the entire lifecycle of a pull request (PR). This lifecycle begins with the first commit and ends with the PR merge.

   • An open PR does not provide a definitive "end point," so calculating metrics for incomplete PRs could lead to inaccurate or skewed results.

2. Consistency and Comparability:

   • By waiting until a PR is merged, Hivel ensures consistency across all calculations. This approach standardizes how time metrics are determined, allowing for fair comparisons across teams and projects.

3. Avoiding Partial Data:

   • Open PRs may not yet reflect the full scope of coding or review activities. Using only merged PRs ensures that metrics are based on complete data, providing reliable insights.

Metrics Breakdown:

Once the PR is merged, Hivel calculates the following metrics based on the first commit date to the merge time:

• Cycle Time: Total time from the first commit to the PR merge.

• Coding Time: Time from the first commit to the PR's submission for review.

• Review Time: Time from the PR submission to the review's completion.

• Merge Time: Time from the end of review to the PR merge.