We’re live on Product Hunt

We’re thrilled to announce that Hiten Shah decided to hunt us on Product Hunt today! Since our last launch, we’ve managed to add Pull Request stats and Tickets stats using the integration with Jira and soon Azure.

Waydev 3.0 - Git Analytics platform for engineering managers | Product Hunt Embed

I would be delighted to have your upvote and know your feedback. Without feedback from our community, we wouldn’t have made it to this point. Thank you, Waydev Community!

Developer Summary Improvements

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.

NEW: Pull Request Velocity Metrics

We've worked with our customers' feedback to develop metrics that reflect the Pull Request Velocity. You can now visualize the average duration for each step of the pull request cycle

We also built quantitative pull request metrics, such as the number of pull requests merged without rebasing, the number of pull requests merged without review, and more.

You can find the Pull Request Velocity metrics in the Developer Performance, Teams Stats, and Repositories Stats reports. Click on the Pull Requests Stats button to toggle the Pull Request Velocity metrics.

NEW: Pull Request Risk

Introducing Pull Request Risk - Monitor the probability of a pull request to cause problems. The Pull Request Risk metric aggregates multiple data points, among the number of commits, the size of the commits, the spread and depth of the changes.

You can visualize Pull Request Risk using the Work Log and the Review Workflow features.

Inactivity Improvement

We've improved the Inactivity 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.

NEW: Team Settings

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.


Work Log improvements

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.

Show Previous EntriesShow Previous Entries