PR/Branch assignments summary (Team)

Modified on Tue, 28 Jan at 11:00 PM

Target Audience

This report is designed for Engineering leaders, Engineering managers, provides an overview of pull request (PR) activity, review efforts, and potential bottlenecks for team members. The chart highlights individual performance and areas requiring attention over the past three months.


Report Overview

The Issue status report serves to:

  1. Highlight Flags: Display flags associated directly with the PRs and code branches (based on code contributions from the engineer).

  2. Indicate Age of PR: Indicates the age of the PR since it's inception, the age of the PR can help the user draw valuable insights into efficiency as well as bottlenecks associated with the PR.
  3. Showcase associated Issues: All the issues that are associated with the PR in the project management tool.


Health Analysis

The report computes the health using:

  • Flags associated with Code branches/PRs (in an active or future sprint) where the engineer is a contributor.


Note: Rules for computing the health can be customized using the report configurator.



Optional Deep Dives

Users can explore a variety of data points across the following categories:

  1. Pull Request/Merge Request Data: Metrics in the PR Breakdown section highlight progress and code quality associated with an issue.

  2. Core Issue Data: Metrics shown in the Breakdown sections, extracted from project management tools (e.g., Jira). These provide insights into execution of the issue and potential impediments for closure.



In addition, deeper insights provides actionable strategies to improve individual and team performance while addressing the highlighted recurring issues:

  1. Recurring Patterns: This suggests a systemic issue rather than isolated mistakes. The recurring nature implies either insufficient resolution strategies or failure to address root causes.

  2. Quality over Quantity: While an engineer is contributing PRs regularly, the high flag count reflects a need to focus on improving quality of work.

  3. Training and Mentorship: Enables the user to focus on bridging the skill gap based on flags associated with the work done by the engineer.



Data sources:

The report integrates data from:

  1. Project Management Tools: e.g., Jira.
  2. Version Control Systems: e.g., GitHub.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article