Teams

Teams is the list of all teams in the organization, available from the main navigation as the "Teams" tab (the same label is also shown as the table title on this page).

Visibility of some elements depends on the organization's configuration and the purchased package. This description assumes all of them are enabled.

AI Adoption

A panel summarizing AI adoption across the whole organization, broken down by team. It shows:

• % adoption: what share of calories (development effort) in the selected period was produced with the help of AI, compared to the previous period.
• AI cal: the sum of calories generated with the help of AI.
• Tokens: the number of tokens consumed by AI tools.
• AI spend: the estimated cost of AI usage in this period.
• A chart compares the adoption trend in the current period against the previous one.

The "Expand" button shows a list of teams, sorted in descending order starting with the one that generated the most calories with the help of AI, with additional indicators (calories without AI, tokens, calories per AI commit, R30 retention split by AI/non-AI, cost per dollar, number of active AI users). The "Hide" button collapses the list again. → AI Adoption

Team health summary

The "Team health summary" section shows the health metrics score for the teams you manage. The header carries an aggregate score, plus a line with the number of active signals and the number of teams they concern.

Node cards are ordered starting with the ones with the most bad signals, twenty per page. Above them are two independent pill filters: state pills with counters, and pills for the individual metrics. Within one row of pills the selections add up, and between rows they narrow the result, so selecting the Critical state together with the Stale PRs metric shows nodes that are critical for exactly that reason. A pill with a zero counter is hidden.

The horizontal bar above the cards shows the distribution of all nodes across the four states at once.

The card of a team with subteams lets you drill one level down without leaving this page. The view then swaps the cards for the subteams of the selected branch.

People belonging to the team being viewed, but not assigned to any of its subteams, are gathered into a single Individual Contributor on {team} card. This way the sum of the cards matches the full composition of the branch, and a participant belonging to several nested teams is counted once.

The section appears only when the administrator has enabled health metrics, and the account manages at least one team.

The full description of the metrics, thresholds and states is on the Health Metrics page.

Teams table

Toolbar:

• Search: searches by team name.
• Calories Type selector: switches which activity the metrics are calculated from: Total / Coding / Documentation. The choice is remembered only for this page, independently of what is selected on the Overview, Project, Participant or Team. → Calories Type
• The filter icon: opens the "Filter" window with separate conditions for each column.
• The gear icon: opens the "Customize table content" window, lets you turn individual metric columns on and off, grouped into categories.
• The down-arrow icon: exports the visible columns and rows to CSV.

Default visible columns: Team Name, Activity, Last Increment Date, R30, Calories (total), Daily Calories / Person, Increments (total), Favourite. By default the table is sorted in descending order by the Activity column.

Clicking a row goes to the Team page for that team.

Statistics available in the table

All the metrics that can be turned on in the "Customize table content" window, grouped into 6 categories exactly as in that window.

Additional information

Column	What it shows	Visible by default
First Increment Date	The team's first activity, from the entire history.	No
Last Increment Date	The last recorded activity, from the entire history.	Yes
Duration	The number of calendar days with activity in the selected date range.	No
Team Capacity	How many people actually worked in the team in this period.	No
Effective Team Capacity	How many people worked on average each business day of the selected period.	No

→ Activity period · Team Capacity

Retention

Column	What it shows	Visible by default
R1	What percentage of added lines of code survived, meaning it was not overwritten or deleted, after 1 day. Each indicator is calculated in a shifted window of as many days as its name states.	No
R7	What percentage of added lines of code survived after 7 days.	No
R30	What percentage of added lines of code survived after 30 days.	Yes
R90	What percentage of added lines of code survived after 90 days.	No

→ Retention

Work Dynamics Indexes

Column	What it shows	Visible by default
Activity*	A composite indicator of the team's overall activity (0-100%), the average of the four metrics below in the same category.	Yes
Presence	What % of business days had any activity.	No
Effort	How intensive the work was relative to the assumed target (calories per business day).	No
Output level	How regularly increments were produced relative to the assumed target.	No
Work Rhythm	How evenly activity was distributed over time, without long gaps or clusters.	No
Business Days	The number of business days in the selected period, excluding weekends and holidays.	No

*Activity is also the table's default sort criterion.

→ Work Dynamics Indexes

Calories

Column	What it shows	Visible by default
Calories (total)	The sum of the development effort (Calories) of the whole team in the selected period.	Yes
Daily Calories / Person	The average daily effort per person in the team.	Yes

Increments

Column	What it shows	Visible by default
Increments (total)	The total number of recorded changes (commits, tickets, etc.) in the team.	Yes
Daily Increments / Person	The average daily number of increments per person.	No

Lines

Column	What it shows	Visible by default
Lines (total)	The total number of lines of code changed in the team.	No
Daily Lines / Person	The average daily number of lines per person.	No

→ Calories, Increments and Lines

This table does not have a "Flow Metrics" category: Lead Time and Cycle Time are metrics calculated only at the project level.

See also

• Team: details of a single team, after clicking a row in the table
• AI Adoption