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.
Change work item state based on child work item state change
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.
Modern, fast, mobile-friendly UI
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.
General availability of multi-stage pipelines UX
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:
Streaming for Azure DevOps Auditing
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.
Artifacts events in the auditing service
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 GA and project-scoped feed creation UX
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.
Sprint Burndown widget with advanced configuration
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.
Create Dashboards without a team
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.
Pay for users once per user across organizations under the same Azure subscription
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.
Please support Markdown especially on Azure Boards Description. Thanks!
It was planned for awhile, but was moved to Cut on 7/12/2019: https://dev.azure.com/mseng/AzureDevOpsRoadmap/_workitems/edit/1221138/
Judging by the history of that Work Item, it looks like they may have attempted to implement the feature in the past.
I wish the public backlog provided more info on why the item was ultimately cut, especially because it’s a popular request.
It is back in our roadmap but we don’t have a delivery date. I passed your feedback to the team. Thanks
When will Deployment Groups in YAML be supported?
See this GitHub issue.
We need to use on-premises infrastructure at our organization. Unfortunately, we can’t switch to YAML pipelines completely because they can’t deploy to our on-prem infra.
We will be rolling out support for VM resource in Environments soon (3-4 weeks). With that you will be able to target on-premises or any cloud IaaS resource using YAML pipelines. In case you are interested for early preview access, you can DM me on twitter:@r00pesh
Is “Pipeline Analytics” feature still on track for Q4 as mentioned in here https://docs.microsoft.com/en-us/azure/devops/report/powerbi/data-available-in-analytics?view=azure-devops?
Hi Sumeda, I will provide more details soon about Pipelines Analytics.
@Gloridel, I’m having a hard time finding in your roadmap any features to support manual deployment. Currently, I use the “Manual only” pre-deployment trigger through the classic release UI. The multi-stage pipelines do not yet support this. Is there a plan to add feature parity for this specifically?
Hi Andrew, manual validation in YAML piplelines has been added to 2020 Q1.
I think Azure DevOps its a great tool but it has several flaws now than stops us for using in our organization (+300 developers)
Not able to define as code the release pipelines (yaml)
No multicloud “elastic agent” support like Jenkins and Bamboo. We use azure and aws and CloudBees-Jenkins supports this feature years ago
Not able to use any docker hub image or linux distro for construction (only ms supported ones)
If you can combine the no-manteinance saas model, the nice ui, agile features and release management model with the flexibility and cloud-agnostic model like Jenkins or Bamboo your competitors will have a hard time. Keep up the good work.
Hi Darío, thank you for your feedback. You can continue to provide feedback in the Developer CommunityDeveloper CommunityDeveloper Community. Take a look at the What’s new for Azure Pipelines blog post for more details about Multi-stage YAML pipelines.
Where can we discuss and ask questions about upcoming changes? I’m interested in the runtime parameters fix (https://dev.azure.com/mseng/AzureDevOpsRoadmap/_workitems/edit/1505234/) and want to know if it will allow us to do conditional inserts based on queue-time variables.
Hi Marco, it will allow conditional inserts on runtime parameters, but not on queue-time variables.
I’m working for a company with specific constraints.
We want to manage our IP adresse in inbound of Azure key vaults firewall
The question is :
Is it possible to use AzureDevops with PrivateLink in order to access KeyVault?
This is a security question because we don’t want to allow all trafic on the key vault firewall.
Do you have a solution for this if it’s not possible ?