NEW: Team Insights, New Heatmap, Jira Webhooks, New Sharing Index

We’re thrilled to announce the latest updates to Waydev. Here’s what’s new:

• New Team Insights: Improved Team Insights report for a comprehensive summary of team activities, including a new widget: Work Heatmap.
• Improved Sharing Index: Improved Sharing Index to assess and promote team collaboration on code reviews.
• New Jira Webhooks:  Real-time Jira data updates directly in Waydev.
• New Heatmap:  Improved widgets in Team Insights, Contributor Insights, and the Dashboard for clearer activity tracking of your teams.

New Team Insights

The Team Insights Report provides a comprehensive summary of your teams’ recent activities, enabling you to better understand their performance and progress.

In the snapshot section of the Team Insights Page you will see:

• The selected team’s Cycle Time;
• The selected team’s Work Heatmap;
• The selected team’s total number of commits;
• The selected team’s Pull Request Activity;
• The selected team’s Most Active Pull Requests.

Cycle Time
The Cycle Time indicates a team’s development velocity. The Cycle Time is the sum of four metrics, each of these metrics corresponding to a stage in the software development process: Coding; Pickup; Review and Deploy.

New: Work Heatmap

The Work Heatmap offers more clarity on the days a team has been active based on commits, PRs, and tickets. Each column represents a week, and you can see all activity from the past 5 weeks.

Commits Activity

Commits Activity = the total amount of commits done by the team. 

The Commits Activity widget includes the average of the last 8 weeks as well as a comparison with the previous 8 weeks.

Pull Request Activity

Pull Request Activity= the total amount of Pull Requests from the last 8 weeks.

Most Active Pull Requests
The Most Active Pull Requests list displays a list of the top 10 most active pull requests from the last 8 weeks.

Improved Sharing Index

The Sharing Index is a metric designed to assess how well your team collaborates on code reviews. It quantifies the distribution of reviews across your team members and considers factors that promote fair and active participation. A higher Sharing Index indicates a more collaborative environment.

How It Works:

I. Gathering Data:

• We start by collecting information on all pull requests (PRs) merged within a specific time period.
• For each PR, we record who submitted it (submitter) and who reviewed it (reviewers).

II. Calculating the Base Sharing Index:

• We count how many reviews each submitter received.
• Using these review counts, we calculate the Gini coefficient, a statistical measure of inequality. In this context, it tells us how evenly the reviews are distributed among submitters.
• We subtract the Gini coefficient from 1 to get the initial sharing index, a value between 0 (unequal distribution) and 1 (perfectly equal distribution).

III. Adjusting for Fairness:

• Reviewer Participation: We want to encourage everyone who can review code to participate actively. We calculate the ratio of active reviewers (those who have done at least one review) to the total available reviewers. This ratio is then adjusted to a value between 0 (no participation) and 1 (full participation). This adjustment encourages a higher sharing index when more team members are actively reviewing.
• Submitter Distribution: We aim for a balance where each submitter’s code is reviewed by various team members. We analyze two aspects:
  1. Variety of Reviewers: We calculate the Gini coefficient based on the number of different reviewers each submitter had. A lower Gini coefficient means a more diverse set of reviewers for each submitter.
  2. Number of Reviews: We calculate the Gini coefficient based on the total number of reviews each submitter received. This ensures no submitter is overwhelmed with a disproportionate amount of reviews.
• We average these two Gini coefficients and normalize them to a value between 0 (uneven distribution) and 1 (even distribution) (the resulting value is then subtracted from 1 and normalized by the total number of pull requests, the result is then capped between 0 and 1). This adjustment promotes a higher sharing index when reviewers are spread out more evenly across submitters.

Why Normalize by Total Pull Requests?

This normalization step helps put the inequality in perspective. If a team has many PRs, a slight imbalance in reviewer distribution is less concerning than if they had only a few PRs. By dividing by the total number of PRs, we account for the scale of the review process.

IV. Final Sharing Index:

We multiply the initial sharing index by both adjustment factors. This gives us the final Sharing Index, a value between 0 and 1.

What the Sharing Index Means:

• Closer to 1: Your team has a highly collaborative code review process. Reviews are well-distributed, with active participation from all available reviewers, and a good balance of different reviewers for each submitter.
• Closer to 0: Your team’s code review process might need some improvement. Perhaps a few people are doing most of the reviews, or some submitters consistently get feedback from the same small group of reviewers.

NEW Jira Webhooks

We are excited to announce the launch of our new Jira Webhooks! Now, you can receive real-time data updates from Jira directly in Waydev.

To generate Jira Webhooks, navigate to Waydev integrations and find the Jira integration you want to set up Webhooks for -> Actions -> Configure Webhooks.

Access this link https://developer.atlassian.com/server/jira/platform/webhooks/ (Jira’s documentation on how to set up Webhooks).

Copy&Paste the link in the URL slot https://hooks.waydev.co/webhooks/{SLUG} – the slug is generated by the app.

For Events, make sure to check all the boxes for:

• Issue: ✓Created ✓Updated ✓Deleted
• Comment: ✓Created ✓Updated ✓Deleted
• Project: ✓Created ✓Updated ✓Deleted
• Board: ✓Created ✓Updated ✓Deleted

For Scope:

You can set a query based on your requirements OR Leave the field empty, and Waydev will be pinged by all your Jira projects. However, we will only process the ticket projects you selected in Waydev.

NEW Heatmap

New Heatmap widgets to provide better clarity on your teams’ activities! We have replaced the Activity Heatmap feature with improved widgets available in Team Insights, Contributor Insights, and the Dashboard. These widgets will provide better clarity on team activity based on commits, pull requests, tickets, reviews, or deployments.