We've added the option to compare engineer stats with team average stats using the Developer Progress feature. This will help you spot underperformers and identify coaching opportunities. Comparing engineer stats with team average stats can also help you discover top performers and recognize their wins.

We've added PR stats in the Team Progress and the Developer Progress features. Learn more about Team Progress and Developer Progress.

If you want to hide developers' names from other users on the platform, you can do it by following this guide.

We've just launched our integration with Azure DevOps Server. Learn more about integrating Azure DevOps Server here.

The Activity Heatmap feature now displays the time zone used for the stats.

We added Throughput, Productive Throughput, and Commits/ Active Day in Targets. Learn more about Targets.

You can now view more than 5 engineers in the Work Log, using the 'Per Page' filter.

You can now sort individual engineer stats in the Dashboard. You can do this by clicking on each metric's name.

We've added trendlines that help you track the evolution for each metric in the Developer Performance, Team Performance, and Repositories Stats reports. Click on any metric to display its trendlines.

We redesigned the Developer Summary feature, adding new metrics and visual enhancements to improve usability. The new Developer Summary metrics include tt100, PRs Merged Without Review, PR Comments Addressed, and more. You can learn more about the new Developer Summary metrics here.

We've improved the Activity feature by adding more events that label an engineer as active.

We are now looking at Commits, Pull Requests, Pull Requests Comments/ Reviews, Tickets, and Ticket Comments.

We’ve created a new visualization for the Activity Heatmap. The new visualization displays commit activity as an individual weekly heat map.

Team Settings enable users to assign settings for a particular team. With the Team Settings you can:

• Ignore commits based on a message (This is based on a regex. ex: /\bweb\b/i, result: all this team's commits that have a message which contains the word "web" will be ignored)
• Ignore commits based on LoC (By default, we ignore commits with more than 8,000 LoC. Insert a positive integer to ignore this team's commits that have more LoC than the positive integer selected.)
• Include merges into reports (By default, we don't include merges into reports, except for the Work Log. If you insert 'yes', we will include merges into this team's reports.)
• Select the stats timezone (By default, we display stats according to the local time of execution. ex. If you are located in Los Angeles (PDT) and you have a team located in Chicago (CDT), selecting the PDT timezone for the team located in Chicago will convert that team's stats to the PDT timezone.)

You can assign team settings for both existing and new teams.

Assigning team settings for existing teams 

Step 1: Navigate to the Engineers page, in the Project section.

Step 2: Select a team from the team list, and then click Edit on the right side of the page.

Step 3: In the modal, select Settings. Insert the values you want to assign, and click Update.

Assigning team settings for new teams 

Step 1: Navigate to the Engineers page, in the Project section.

Step 2: Click Create new team.

Step 3: In the modal insert the team name and description. Then, click Settings. Insert the values you want to assign, and click Create.

You can now navigate to an engineer's Developer Summary profile by clicking on their name & avatar in the Work Log.

You can now access your commit in the Git provider by clicking the 'Go to Commit' button in the zoomed-in view of the Work Log.