Yesterday, we published updates to our product roadmap. It outlines our plans for the next two quarters, and future investments. The features listed below are a few highlights of what we plan to deliver in Q3. Visit our product roadmap for a complete look at the list of features for Q4.
We are excited about the future and the impact the features we plan to deliver will have on our customers’ success!
For the last several months our team has been focused on collecting feedback about the New Boards Hubs and addressing bugs based on this feedback. This quarter we plan to turn on the New Boards Hubs as the default experience for Azure Boards. Check out this blog post to learn how you can turn on this feature.
In this quarter, we plan to bring you features that will help you improve the security of your Azure Pipelines. We will work on introducing support for Workload Identity federation for Azure service connections, bring improvements to YAML pipelines’ environments and Approvals & Checks, add controls for building PRs (pull requests) from forked GitHub repositories, and make the permissions for queuing pipelines more fine-grained.
Chart click thru to results by section
Over the years, there has been a consistent demand for the ability to select a specific subset of the work item chart. We are thrilled to announce that in this quarter, we are developing a drill-down functionality that will let you explore your work items in greater detail. With enhanced control over filtered query results, our goal is to deliver a seamless user experience that exceeds your expectations.
Rollup columns for query results
In addition, we plan to deliver Rollup Columns in queries. We have received numerous customer requests asking about this feature. This will let you have more complex filtering options based on state or other criteria, allowing for better control and adjustment of priorities. We are excited to provide a holistic view, enabling you to build portfolio-level dashboards using queries.
Currently, you can view code coverage percentage of the various DLL files being tested. However, in the case of monolith repositories, you can have multiple microservices under the same repository. Hence, making it difficult to quantify the code coverage of the individual microservices. Automated testing is solving this problem by highlighting code coverage insights at a source level. This will allow developers to better quantify the code coverage results of their microservices and take mitigation steps accordingly.
To learn more about these and other features we plan to deliver, check out our updated product roadmap at https://aka.ms/AzureDevOpsRoadmap.