Docs
📈 Activity
People

Activity People

The People dashboard provides a detailed breakdown of engineering activity at an individual level. It helps track contributions across team members and ensures visibility into their engagement with the codebase.

Activity People

Data Sources

All activity data is sourced from Git/VCS and Project Management tools integrated with Hatica.

Filters

  1. Date Range Picker: Select a specific time period to view relevant metrics.
  2. People: View activity for individual engineers.
  3. Custom Teams: Filter activities by specific custom-defined teams.
  4. Activities: Select specific activity types such as:
    1. PRs Opened
    2. PRs Merged
    3. PR Reviews
    4. PR Comments
    5. Issues Resolved
  5. Filter Empty Rows: Hide users with no recorded activity during the selected period.

How to infer this data?

Each activity type is color-coded to help users quickly identify activity distribution.

  1. Color and Band Size:
    1. Color coding differentiates activity types, making it easy to spot trends.
    2. Band density represents the volume of activity—packed cells indicate high engagement, while empty cells indicate no recorded activity.
    3. Pill size varies based on task significance—larger pills represent bigger tasks or higher effort, while smaller pills indicate smaller contributions.
  2. Summary Column: The second column summarizes total activities per individual. Engineers typically show high Git activity, while tech leads may have more PR review activity.
  3. Day-Level Summaries: Clicking on a specific day opens the context window with a detailed breakdown of completed activities.

The Commit data only accounts for Remote commits; any commits done on Local Git branches are not included here. So if your team has a habit of doing all development on a local branch and pushing it to a remote branch after a period of time, you may not see any Commit activity.

💡

It might be worthwhile looking into this if you have a practice of developers always using Local branches and pushing code to Remote only after dev completion.

How to Use This Dashboard

  • Track individual contributions across PRs, reviews, and commits.
  • Analyze work patterns over time.
  • Spot irregularities such as extended inactivity or workload imbalance.
  • Hover over activity markers for a detailed breakdown of work done on a specific day.
  • Identify engineers overloaded with PR reviews or with minimal contributions.
  • Monitor potential blockers such as long open PRs or pending reviews.
CodeTeams