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.
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 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.
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.
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 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.
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.
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.
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.