Changelog

Improvements

1. Bird's-eye View 2.0: all metrics in one view

2. New metrics for displaying Backlog tickets. 

Bug Fixes

• Fixed Inconsistent Filter Behavior
• Fixed loading issues
• Fixed graph editing when creating a widget
• Fixed Targets creation

Changelog

Improvements

1. New AI Adoption integrations: Claude Code and Windsurf

2. Incidents & Releases in DORA metrics now also show the source

Bug Fixes

• Fixed dropdown not working when creating metric widgets in dashboards
• Fixed in progress surveys displaying “Survey Not Available” message
• Fixed FTE calculations

Changelog

Improvements

1. We've updated the AI predictability feature

• Redesigned UX
• Now using Claude Sonet AI
• Full ROI traceability

2. Groups replace Projects as the default view in Waydev. When creating a new Group, you can choose whether it will function as an Initiative, Workspace, or Project

Bug Fixes

• Fixed team filters to remain persistent across all pages

Changelog

Improvements

1. Improve Overall App Intuitivity

   • Multiple UX/UI enhancements across Setup, Studio, and Delivery sections for better navigation and clarity.
2. Fix Jira Transition Workflows from GitHub
3. Cleanup - Removed unused code references for performance and maintainability.

Bug Fixes

1. Fixed Story Points Metrics not showing data for Azure Boards
2. Fixed Targets page not loading when creating a new target
3. Fixed Ticket Projects pagination
4. Fixed an issue with ticket types not displayed in the “Ticket Type Assignment” step for integrations.

We’ve updated the metric previously known as "Cycle Time" to "Lead Time for Changes" to better reflect its purpose and provide more clarity. This change ensures that the metric aligns with industry standards and offers a more accurate understanding of the process.
Thank you for your continued trust and support!

We’re excited to introduce Sprint filtering in Waydev. You can now filter any report by sprint, aligning insights with your team’s sprint cadence.This gives you a clearer view of progress, trends, and performance—broken down sprint by sprint—so you can better assess how initiatives are moving, To configure this, set your sprint duration (e.g., two weeks) and the start date of your last sprint.

You can now customize the Team & Contributors Insights reports with any Waydev metric—giving you the control to focus on what drives performance across your engineering organization.

This report allows you to benchmark team delivery and health, with the added flexibility to select the metrics that align with your goals—offering a more complete view of your teams’ activity and performance. Whether you're tracking trends, identifying areas for improvement, or benchmarking team performance, this update helps you make more informed, data-driven decisions at scale.

Since the moment we started back in 2017, we realized that we’ve done a lot of work to improve the productivity of software engineering teams, and now we have a complete set of features in four categories of value: Health, Delivery, Planning, and Automation, all covering important aspects of your team’s performance.

We improved the way we calculate the 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. By analyzing the distribution of reviews among submitters and the participation of reviewers, it provides a score from 0 to 1. A higher score indicates well-distributed reviews and active involvement from all team members.

Learn how the new Sharing Index is calculated here.

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

In the snapshot section of the "Team Insights Page" you will now 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.

Documentation here.