We’ve added a new Work Log view to help you keep track of your team’s ongoing work and provide better visibility into everyone’s contributions. This view offers a real-time snapshot of activity across the entire team, making it useful for both managers and developers.

🔍 How it works:

The Work Log displays each contributor’s activity, organized by day, with activities grouped into three categories:

• Opened PRs (green hexagons)

• Merged PRs (purple hexagons)

• Code reviews (speech bubble icons)

The size of each icon varies based on the PR size, giving a clear indication of the effort involved. Hovering over an icon provides more details about the PR, including:

• Status

• PR title

• Repository name

• Number of comments

• Size

💪 Why it's useful:

For leaders:

• Improve workload distribution: Gain context to better balance workloads if someone is regularly overloaded.

• Detect when someone might be struggling: Spot low activity from a developer over several days, which could indicate they’re stuck or facing challenges, allowing you to proactively offer support.

• Prepare for 1:1s & retrospectives: Gather concrete, data-backed insights to support feedback, career growth discussions, and workload adjustments.

• Recognize effort, not just volume: Make sure big contributions are acknowledged, not just the number of PRs.

For individual contributors:

• Make your work visible: Use the Work Log as a “brag document” to highlight significant contributions during 1:1s or performance reviews.

• Support promotion cases: Provide concrete evidence of high-impact work and consistency over time.

• Document growth: Track your progress over time and identify areas where you've improved or taken on more complex tasks.

🚩 What this view is not for:

The Work Log is not intended to measure individual productivity. It only reflects activity related to PRs and code reviews. It doesn’t account for essential work outside of code contributions, like planning, meetings, research, or documentation.

Use it as a tool to improve collaboration, provide feedback, and recognize effort — not as a strict performance metric.