Team Activity

Team Activity helps you understand how each team member contributes to your codebase: who’s actively coding, opening PRs, reviewing, and where potential leaders are emerging. This view is available from Teams → Activity in LinearB.

TL;DR – What you can do here

• See all members of a team, including previously inactive members.
• Filter by time window and specific members.
• Understand an individual’s impact across branches, repos, PRs, and reviews.
• Spot potential team leads by review depth and review activity.

• Jump directly to Edit team to adjust membership as needed.

Overview

Here you can view all team members and their contributions. You'll learn how to filter by time and member, as well as see inactive members and their activity history. Brandon highlights key metrics such as active branches, code changes, and PRs opened, which are crucial for understanding each member's impact. 

We encourage you to explore these insights to better understand team dynamics and identify potential leaders based on their review depth and activity. 

Please take some time to familiarize yourself with these features as you settle into your role and reach out to our team with any questions.

Let you Manager of Solutions Architects walk you through the Team Activity section of our dashboard.

---

How to open Team Activity

1. In LinearB, select the team from the team picker  in the upper righthand corner.
2. Go to Teams → Activity.
3. Team Activity loads for the team selected.

By default, you’ll see a time filter at the top and a list of members for the selected team. You can adjust the time filter or remove it to view “all time” data.

---

Filters & member list

Date filter

Use the time filter at the top of the page to choose the period you want to analyze. Removing the time filter shows metrics aggregated for all time for that team.

Member filters

• Member filter (left side): narrow the view to one or more specific team members.
• Show inactive members: toggle to include people who were on the team in the past but are no longer active members.

When you enable Show inactive members, the table includes everyone who has ever been on that team, so you can still review their historical activity.

---

Understanding each member row

Each row in the Team Activity table represents a single contributor and summarizes their work within the selected time window (or all time, if no filter is applied).

Membership & Git accounts

Hovering a member’s name shows:

• Teams: how many teams they belong to (for example, “member of 2 teams”).
• Git accounts: how many Git accounts LinearB has detected for that person. This is useful when a developer commits from multiple places (local, cloud, or on-prem servers) using different email identities.

Use this information when performing user merging in Company Settings so that all of a person’s Git identities are correctly mapped to a single LinearB user.

WIP (active branches)

The Work in Progress (WIP) column shows the number of active branches for that contributor in the selected time window. If no time filter is applied, this reflects active branches across all time.

Important: In Team Activity, WIP refers to active Git branches, not Jira or project management “work in progress” states.

Active Days

Active Days counts the number of days in the selected period where the contributor had activity in the repositories. Activity includes:

• Making commits
• Creating pull requests (PRs)
• Creating branches
• Adding comments

This gives you a quick sense of how consistently someone is working in the codebase over time.

Code Changes

Code Changes shows how many code changes the contributor has made (for example, lines or chunks of code changed) within the time range.

Use this alongside Active Days to differentiate between light, occasional changes and heavier coding activity.

Repositories

The Repositories column shows how many repositories this contributor has committed to in the selected period.

This can highlight specialists who focus on a single service versus engineers who contribute across many repos.

Cycle Time

Cycle Time is the contributor’s average cycle time across their Git changes in the selected period.

Shorter cycle times typically indicate smoother flow from first commit through review and merge, while longer times can signal bottlenecks or slow review for that person’s work.

Work Breakdown (New, Refactor, Rework)

The Work Breakdown section shows what type of work a contributor tends to do:

• New work – net new code (often feature development).
• Refactor – structural or quality improvements to existing code.
• Rework – changes to recently added code (for example, fixing issues or follow-up adjustments).

Example: if a member shows a very high percentage of new work, they may be heavily focused on feature creation, while higher refactor or rework percentages can indicate attention to code quality or follow-up fixes.

PRs Opened

PRs Opened is the number of pull requests this contributor has opened in the selected time period.

This helps you see how often they are submitting work for review.

Reviews

The Reviews column counts how many PR reviews the contributor has performed on pull requests that are not their own.

This is a key signal for identifying engineers who regularly support others by reviewing their work.

Review Depth

Review Depth measures how detailed a contributor’s reviews are, based on the average number of comments per review.

Example: if someone reviews one PR and leaves one comment, their review depth would be 1.

In practice, you’ll often see emerging leads and senior reviewers with a review depth around 1–2 comments per review, coupled with a higher number of total reviews.

Tip: Look for contributors who both review many PRs and maintain a healthy review depth. These are often your de-facto code stewards and potential team leads.

---

Editing team membership from Team Activity

From the Team Activity view, you can click Edit team to update the team’s membership. This takes you to the team configuration screen in your Company Settings where you can add or remove members.

---

How to use Team Activity in practice

• During onboarding: New managers can quickly see who is most active, which repos they touch, and who reviews code across the team.
• Identifying leaders: Use Reviews and Review Depth to spot engineers who frequently review and provide thoughtful feedback.
• Balancing workload: Compare WIP (active branches), Code Changes, and Active Days to ensure work is not over-concentrated on a few individuals.
• Cleanup & identity hygiene: Use the Git accounts info to find users with multiple Git identities and consolidate them via user merging.

---

If you have questions about how a specific metric is calculated for your organization, capture a screenshot of the Team Activity row and contact your LinearB team or LinearB Support.