Use cases

🤔 Have a question?

Join our community on Discord

Book a personal demo

2022 Code analytics software | Codigy. All Rights Reserved, Codigy UAB ©

Team health

The gist

Understanding the structure of teams & tribes is important. Codigy uses this information to map the modules within your codebase and identify collaboration bottlenecks.

Team health provides instruments to:

  1. Organize engineers into Teams and Tribes;

  2. Clean-up git sources (in case engineers contribute from multiple GitHub/Bitbucket/GitLab accounts);

  3. Understand basic activity patterns of the teams;

Contributor entity

A contributor is a git source that can be an engineer or a bot (e.g. Jenkins, dependabot). Sometimes engineers deliver work using multiple accounts. For convenience, such sources can be merged.


  1. Last active stamp - shows the timestamp of the last action that was detected and processed by Codigy. Helpful indicator while configuring/updating team structure & merging contributor sources.

  2. Source indicator - shows if there are any unconfigured sources that look similar (potential merge target, i.e. if an engineer is contributing from an alternate GitHub account).

  3. Burnout indicator - shows if there were at least two days within a week, where no actions were detected from the selected Engineer. While it doesn't cover 100% of cases (Codigy can't detect work made outside of git), it can be a handy indicator to keep the team healthy.

The number of work hours/days or individual activity metrics can not be determined from this💩 Our apologies to productivity-frenzy managers, we don't believe this has anything to do with efficiency 🤷‍♂️


  1. Merge - any number of sources can be merged. This is handy even if the contributor only works from one account because some actions will be identified as separate sources (i.e commits, PRs and comments will be grouped into three different sources).

  2. Link with dashboard user - this associates the contributor with a dashboard user. The user's Name and Profile picture will be displayed in analytics.

  3. Remove from analytics - contributor will be removed from analytics. In case a new activity will be detected, the contributor will re-appear as unconfigured.

  4. Team - each contributor can be assigned to a single team. A contributor can be re-assigned or unassigned at any time.

Team entity

A team is a group of engineers. The team is one of the key entities for which Codigy will track metrics and produce analytical insights.

For example:

  1. Codebase & Process health analytical lenses have dashboards specifically for a team level.

  2. Daily Stand-up & Sprint retrospective reports are generated for the team entity.

Team parameters:

Team metrics (within Team health lens):

Tribe entity

A tribe is a group of teams. This is an optional organization unit usually used in larger organizations.

If your organization is using this, you will be able to:

  1. Group your Teams into Tribes (Each Team can be assigned to a single Tribe).

  2. Get a dedicated analytical dashboards for All Tribes or a specific Tribe in Codebase & Process health analytical lenses.

This page was last revised on March 29, 2022

Return to main


Codigy, UAB

A.Jaksto g.9 Vilnius, Lithuania

Suite 346

+370 608 96 491 hello@codi.gy

2022 Code analytics software | Codigy. All Rights Reserved, Codigy UAB ©