Development Metrics

API endpoints for development time and process metrics

Development Metrics

Development metrics focus on the time spent in different phases of the development process, helping teams understand and optimize their development workflow.

Available Metrics

coding-time · string

Time spent coding (from first commit to PR open)

coding-time-p50 · string

Median coding time, in seconds. No aggregation parameter. Response column: coding_time_p50.

coding-time-p75 · string

75th-percentile coding time, in seconds. No aggregation parameter. Response column: coding_time_p75.

pickup-time · string

Time between PR open and first review

pickup-time-p50 · string

Median pickup time, in seconds. No aggregation parameter. Response column: pickup_time_p50.

pickup-time-p75 · string

75th-percentile pickup time, in seconds. No aggregation parameter. Response column: pickup_time_p75.

commit-to-open · string

Time from first commit to PR open

open-to-review · string

Time between PR open and first review

review-to-merge · string

Time between first review and merge

review-time · string

Total time spent in the review phase

review-time-p50 · string

Median review time, in seconds. No aggregation parameter. Response column: review_time_p50.

review-time-p75 · string

75th-percentile review time, in seconds. No aggregation parameter. Response column: review_time_p75.

rework-time · string

Time spent on rework after a review

cycle-time · string

Full cycle time from first commit to merge

time-to-first-comment · string

Time from PR open to the first comment

rework-rate · string

Percentage of PRs that required rework after review

Cycle Time Metric

This example demonstrates how to retrieve the cycle time metric, which measures the full development cycle from initial commit to merge.

Request

curl -X POST 'https://api.bilanc.co/metrics/cycle-time' \
  -H 'Authorization: YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
    "filters": {
      "repositories": [{"repository_name": "repo-name-1"}, {"repository_name": "repo-name-2"}],
      "start_date": "2023-01-01",
      "end_date": "2023-02-28"
    },
    "group_by": ["repository_name", "name"],
    "date_level": "month",
    "aggregation": "AVG",
    "date_field": "pr_merged_at"
  }'

Review Time Metric

This example demonstrates how to retrieve the review time metric, which measures the total time spent in the review phase.

Request

curl -X POST 'https://api.bilanc.co/metrics/review-time' \
  -H 'Authorization: YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
    "filters": {
      "team": ["team123"],
      "start_date": "2023-01-01",
      "end_date": "2023-02-28"
    },
    "group_by": ["team_name"],
    "date_level": "month",
    "aggregation": "AVG",
    "date_field": "pr_merged_at"
  }'

Parameter Notes

date_field · string

Development metrics read from the pull_requests table. Available date fields:

• pr_merged_at: When the PR was merged (default, recommended for cycle time)
• pr_created_at: When the PR was created
• pr_closed_at: When the PR was closed
• first_commit_at, last_commit_at: First and last commit on the PR
• first_review_at: When the PR received its first review
• first_comment_at: When the PR received its first comment

aggregation · string

Required for all development time metrics except the fixed-percentile ones. Accepted values: SUM, MAX, MIN, AVG. rework-rate is a ratio and takes none; coding-time-p50, coding-time-p75, pickup-time-p50, pickup-time-p75, review-time-p50 and review-time-p75 are fixed percentiles and take none either. Response columns are {agg}_coding_time, {agg}_pickup_time, {agg}_commit_to_open, {agg}_open_to_review, {agg}_review_to_merge, {agg}_review_time, {agg}_rework, {agg}_cycle_time, {agg}_time_to_first_comment (all in seconds), rework_rate, and coding_time_p50, coding_time_p75, pickup_time_p50, pickup_time_p75, review_time_p50, review_time_p75 (seconds) for the percentile metrics.

filters · object

Applicable filters for development metrics:

• repositories: Array of {"repository_name": "..."} objects
• member: Filter by author merged user IDs
• team: Filter by team IDs
• squad_ids: Filter by squad IDs
• squad_levels: Filter by squad hierarchy level
• manager_ids: Filter by manager user IDs
• departments: Filter by department names
• sources: VCS source — github, gitlab, bitbucket
• pr_states: PR states — open, closed, merged
• pr_categories: PR category classifications
• pr_ids: Filter by specific PR IDs
• pull_requests_search_term: Full-text search across PR fields
• locations: Filter by employee location
• levels: Filter by employee level

Common Use Cases

• Track Cycle Time Trends: Monitor how development cycle time changes over time
• Identify Bottlenecks: Find which part of the development process takes the longest
• Compare Team Performance: Compare cycle times across different teams or repositories
• Set Performance Goals: Establish baseline metrics and set improvement goals