Azure DevOps Roadmap update for 2019 Q4
Azure DevOps Roadmap update for 2019 Q4
We are continuously investing in Azure DevOps, this quarter we plan to deliver very exciting enhancements and features across our services. The features listed below are a few highlights of what we plan to deliver in Q4. Visit the Features Timeline for a complete look at the list of features for Q4. Each feature links to the public roadmap project where you can find more details about each item.
We are addressing the feedback that you provided in the Developer Community about automatically changing states based on changes to linked work item states. For example, if all the child work items are set to closed, then the parent work item state will automatically be changed to closed.
We will be changing the Repos landing pages to include a more modern, fast, and mobile-friendly UI. The pull request details pages will include changes to the overview, files and commits tabs. In addition, the commit details and branch compare pages will be updated with the new UI.
We’ve had great feedback about multi-stage pipelines since we deployed in May. This quarter we will address some of the key features based on this feedback. The areas that we will improve are logs page and overall navigation. We will also continue to invest in features that get us to parity with classic pipelines by letting you skip stages when you start a manual run. In addition, we will transition to opt-out and general availability.
Auditing is now in public preview and we’re continuing to make big investments in this quarter. Specifically:
We will continue to invest in auditing for pipeline events by building streaming for auditing. Streaming will let you send your auditing events to first- and third-party Security Incident and Event Management (SIEM) tools. The use of these tools along with auditing will allow for anomaly detection, trend visualization, and more! We plan to support streaming connectors for Splunk, Azure Log Analytics (with the ability to connect to Azure Sentinel), and Azure Event Grid.
In addition, We will make the auditing capabilities in Azure Pipelines stronger by adding audit events for pipelines and releases, like pipeline edited, run started, checks completed, approval completed, stage completed, and more.
Lastly, we will invest in auditing Azure Artifacts. We’ll focus on auditing scenarios around permission changes, feed, upstream, and package create, update, and delete.
We will release the GA version of Pipeline Artifacts for Azure DevOps Services. Thanks to your feedback during public preview, we fixed issues and further expanded functionality. Pipeline Artifacts uses existing tooling in Azure Pipelines to dramatically reduce the time it takes to store outputs from builds and will officially take the place of Build Artifacts after some transition work. See the Pipelines Artifacts documentation to learn more.
This quarter we will officially release the GA version of Pipeline Caching. We will complete work based on the feedback gathered during the preview and make caching efficient and easy to use.
Public feeds general availability brings the ability to add public feeds as upstream sources from other Azure Artifacts feeds. With public feeds, we will also release the UX for creating project-scoped feeds. Project-scoped feeds will be the default for feeds, which will follow the visibility of the parent project. See the feeds documentation for more information.
Now that we’ve added rollup to your backlog, we are bringing it to your Kanban cards. For example, on the Features board, you’ll be able to view progress bars and sums directly on the Feature card.
The new Sprint Burndown widget will support burning down by Story Points, count of Tasks, or by summing custom fields. You will be able to create a sprint burndown for Features or Epics and configure the team to allow for displaying sprint burndowns for multiple teams on the same dashboard. In addition, you will be able to resize it up to 10×10 on the dashboard.
You’ll be able to create a dashboard that is not associated with a Team and control who can manage or edit the dashboard. The dashboard will be visible to everyone and will let you share and mark as favorite like other dashboards.
Make a copy of a dashboard within a team, to another team, or to another team project.
We have been incrementally rolling out the new per-user billing model over the last 4 months, starting with the transition from monthly to daily billing, and most recently with the change from license purchase to assignment based billing. This quarter we will move out of private preview and enable opt-in to multi-org billing via billing administration.
We appreciate your feedback, which helps us prioritize. If you have new ideas or changes you’d like to see, provide a suggestion on the Developer Community, vote for an existing one, or contact us on Twitter.