Understanding PRs/MRs in Teambit
By default, Teambit's software delivery metrics consider all Pull Requests (PRs) or Merge Requests (MRs) that target a repository's default branch. This setting can be customized per repository.
This configuration can be adjusted using regular expressions (regex) to define source and target branch pairs, allowing teams to tailor which PRs/MRs are included in the metrics based on their specific workflow.
Which Metrics Use This Configuration?
Most of Teambit's software delivery metrics rely on this configuration. The exception is the Dashboard, which displays all work to provide a more comprehensive view of the team's activity.
Key metrics include:
Cycle Time: The total time from the start of development to production deployment.
Subcycles: Intermediate stages within Cycle Time, such as Coding Time, Review Time, and Deploy Time, helping to identify bottlenecks and optimize workflows.
Quality Metrics: Measurements related to the Development Process and PR/MR Review Process.
Work Distribution: Insights into how the team’s time is being allocated across different types of work.
Why Configure PR/MR Selection?
The default setting covers most cases, so modifying it is usually unnecessary. However, customizing the PRs/MRs included in the metrics allows teams to better align measurements with their actual workflow, providing benefits such as:
Flexibility for different methodologies: Teams using Git Flow, trunk-based development, or hybrid models can define which branches to track based on their process.
Inclusion of special workflows: Some teams may want to include hotfixes or other exceptions that are typically excluded from standard measurement methods.
More precise analysis: Filtering out PRs/MRs that don’t reflect the main development cycle helps improve metric accuracy and interpretation.
How to Modify This Configuration in Teambit
Teambit allows teams to configure these filters using regex to define source and target branch pairs. This means you can specify patterns to determine which PRs/MRs should be included or excluded from the metrics.
To modify this setting, contact our team. We’ll guide and assist you with the change.
With this flexibility, Teambit enables each team to tailor its metrics to their specific needs, ensuring that the insights generated are truly valuable for decision-making.