Azure DevOps 2023 Q2 Roadmap update
Yesterday we published an updated list of features we plan to deliver in Q2. Each title includes a link where you can find details about each feature. We expect that this will help bring visibility into the key investments for the upcoming quarter.
GitHub Advanced Security
We are very excited to announce that GitHub Advanced Security for Azure DevOps will be moved into public preview! GitHub Advanced Security for Azure DevOps is a suite of developer security analysis tools integrated directly into Azure DevOps to protect your Azure Repos and Pipelines. With GitHub Advanced Security for Azure DevOps, we bring the same secret scanning, dependency scanning, and CodeQL code scanning capabilities of GitHub Advanced Security right into Azure DevOps.
Service Principal and Managed Identity support (public preview)
Service Principals and Managed Identities can now be used to authenticate with Azure DevOps. As an alternative to personal access tokens (PATs), these Azure Active Directory identities enable teams to gain access to your Azure DevOps organizations acting as their own application, not as a human user or service account.
Markdown support for work item discussion
The ability to use Markdown in the work item discussion has been a frequent request over the years. In this quarter we are excited to make it a reality. The new Markdown editor will replace the existing HTML editor for all new work item comments. We will also be providing a way to convert comments from HTML to Markdown.
Track repo cloning
A frequent request that we get from our customers is to know when someone clones a repo. In Q2, we plan to enhance the repos experience by letting you know how many times a repo is cloned and by whom.
In-product recommendations for secure settings
In pipelines, we continue our investment in security. Azure Pipelines support several settings at the pipeline, project, and organization level to help you secure your pipelines. This quarter we will include in-product experience to provide information about when settings don’t follow the recommended values.
Support for Cargo package manager for Rust
We will continue to invest in the security of the packaging platform by adding native support for additional protocols based on your requests. This time, we will be including support for the Cargo package manager for Rust.
Option on Burnup, Burndown, and Velocity charts to included resolved as completed
As we listened to your feedback from the Developer Community, we heard that you wanted the ability to account for resolved as completed in the Burnup, Burndown, and Velocity charts. This request has been prioritized and is currently in our roadmap for Q2.
Improved support for viewing code coverage directly in Azure DevOps
Code coverage is useful to help understand how well your suite of automated tests is covering your codebase. Currently, code coverage results for automated tests run within Azure Pipelines are not well supported across the wide variety of test runners and file formats in use today. We’ll be improving support for publishing code coverage from a wider variety of sources and making the results available directly within the Code Coverage tab in Azure Pipelines.
To learn more about these and other features we plan to deliver, check out our updated product roadmap at https://aka.ms/AzureDevOpsRoadmap.
I’m going to take a guess an say this is the RoadMap for DevOps [Services] not for [Server].
Any RoadMap for the [Server] version you want to share, or maybe, a Time Line for [Services] coming to GCC High?
Hi Alex, the roadmap is not for Azure DevOps Server. Azure DevOps Server ships from a sprint release but we don’t have a date yet or the list of features we will include with the next release.
Are you going to address the multiple issues around the test cases authoring? There is a consensus in my company about the poor experience about writing test cases. We are not talking about small glitches, writing test cases is really a challenge and frustrating due to user interface glitches and strange behaviors:
And it has been like this for several years, unfortunately the complaints from 2019 are still valid. It’s a shame because the test runs, reports and runner themselves are rather good but are hampered by the test cases writing.
Thank you for sharing your concerns around Azure Test Plans. My name is Ravi and I’m the Product Manager with Azure Test Plans. We have recently started researching on some of the key issues that are customers have been facing and the first two points mentioned by you have been included into our roadmap. We intend to solve the Test case import functionality and bring in support for MS Excel based import.
We are also going to provide Excel based export of Test cases. Today users can only export Test cases inside a Test suite in CSV format which takes away the formatting of the export file (export to Excel will solve this issue).
For the other issues highlighted, you may see improvements in the speed and UX in incremental updates.
Any plans to improve the support for Universal Package artifacts in the DevOps Artifact Feeds? There are a couple of small missing features that make Universal Package artifacts hard to use. These include:
These three features feel like they’d be straightforward, and would help my team (and others) to ditch Artifactory in favor of Azure Artifacts.
I maintain/manage the firmware builds for a number of embedded Linux systems, and here are the use-cases that I can’t accomplish with Azure Artifact Feeds right now: