Distributions

The Distributions view shows how your team’s work is distributed over time. When set up correctly, it breaks down where engineering effort is going — what percentage of work is focused on tech debt, security, new features, or bugs.

Note: Teams need to manually create labels (e.g., “tech debt”, “security”, “new feature”, “bug”) within their GitHub repositories. Once PRs or issues are labeled accordingly, the Distributions view will automatically categorize and visualize that data.

Where to Find It

Go to Allocations → Distributions in the left sidebar.

How It Works

The Distributions page pulls data from all PRs or issues within your selected date range. It groups them by label or type to calculate how much work falls into each category.

Each colored section in the chart represents a different type of work:

• Bugs — fixes and patches
• Tech Debt — refactoring or cleanup
• Security — vulnerability and dependency fixes
• Enhancements — improvements or new functionality

Hover over each segment to see the exact percentage and number of PRs associated with that label.

Filters

Date Range

Choose the time period you want to analyze — for example, a sprint or week range. All metrics and charts refresh automatically as you adjust the dates.

Repository Filter

Select one or multiple repositories to narrow your view. This helps you isolate work across different codebases or projects.

User Filter

Filter results by a specific team member to see where their work was allocated. Helpful for understanding workload balance or individual focus areas.

Toggle Chart Type

Switch between two visualization styles:

• Donut Chart — shows percentage breakdowns by category
• Bar Chart — shows changes in distribution over time

GitHub / Jira Toggle

Switch between GitHub and Jira to control the data source:

• GitHub — categorizes work by pull request labels
• Jira — categorizes by issue types

Interpreting the Data

Pull Request Table

Scroll below the chart to see a detailed list of pull requests that make up the data. Each row represents a single PR with these columns:

• Label Name — which category the PR belongs to
• Title — the pull request name from GitHub
• Repository — which codebase the PR originated from
• Author — who opened or merged the pull request
• PR Size — lines added (+) and removed (–)

You can sort by any column, use the search bar to find a specific PR, and use pagination to navigate large datasets.

Troubleshooting