Azure DevOps Roadmap update for 2020 Q3
As part of our ongoing commitment to Azure DevOps, we’d like to share with you some key features we’re planning on delivering over the next quarter. Each of these highlighted features includes links to our public roadmap project where you’ll find more details on the item and where you can check its status.
In Q3, we are adding REST APIs for managing the lifecycle of personal access tokens. This will include the ability to create new personal access tokens; and to rotate, renew, and revoke existing ones.
This feature was covered in the Q2 quarterly blog update, but due to shifting priorities in Q2, we did not finish the work. Follow the link to learn more about the feature.
In Q3, we are increasing our investments in Boards to provide a first class roadmap/timeline feature. Our work will focus on improving and enhancing the capabilities of Delivery Plans. Q3 will be the first wave of investments where the focus will be bringing Delivery Plans into the core product (instead of an extension). The second wave of features will be focused on new functionality and value that have been long time requests from our customers.
Q3 enhancements include:
- Bring Delivery Plans into the core Azure Boards product instead of having to install an extension
- Allow work items to span iteration boundaries
- Support a minimum of 25 team backlogs on a single delivery plan
- Filter by Parent
- Give stakeholders read-only access to delivery plans
Late Q3 and early Q4 features include:
- Display rollup information on the work item cards
- Provide a condensed view for better viewing of large plans
- Provide a dependency tracking experience across work items with predecessor and successor link types
In Q2, we rolled out a preview of scale-set agents – our first version of elastic agents based on VM scale sets. Since then, the adoption of this feature has been gradually increasing. Thank you to all of you that have provided feedback during the preview period. Based on the feedback, here is our plan for Q3:
- We will add scheduling to the scale-up operation so that you do not have to run the same number of agents during peak hours and after peak hours
- We will roll out elastic agents that run in containers on a Kubernetes cluster. Besides being able to use your infrastructure more efficiently, this will also improve the speed of scaling operations
- Finally, we will improve the diagnosability of elastic agents by exposing background logs and possibly a few more knobs for you to control
Azure Test Plans
The new persona-based Test Plans page will be introduced as the default experience with a revamped user interface that provides new views and toolsets for tasks such as authoring, tracking, and executing. The new page is clutter-free and integrates seamlessly with the rest of Azure DevOps. As an addition to the pre-existing page, the new page brings in the following new capabilities:
- Copy Test Plans: This feature allows the user to copy/clone a Test Plan within a project
- Import test suites: You can now reuse the suites which are created already and import them into the current test suite/test plan using Import Test cases
- Copy/clone test cases: You can now copy or clone a test case across test suites, test plans, or projects
- View linked items: For each test case, you can view the linked bugs, test suites, or requirements
- Import/Export test plans from/to CSV files: With the help of this feature you can export the existing test cases to Excel CSV file, make changes to the CSV file and then import the file back into the suite. There are many other use cases of this functionality. New test plans page – Azure Test Plans
We have been previewing Upstream sources with Universal Packages feature for some time now, and we are glad to announce that we will be making it generally available by the end of September. Upstreams within Azure Artifacts enable you to manage all of your product’s dependencies within a single feed. In that one feed, you can store the packages you’ve produced and consumed from either remote feeds, or other authenticated feeds. This feature provides simplicity, determinism, provenance, and peace-of-mind to Azure Artifacts customers.
Now, we’ve added the ability for customers to use Universal Packages (Upacks) as an upstream source. Up until now, customers were only able to use npm, NuGet, Python, and Maven package types as upstream sources.
This feature is available for use with feeds within the same Azure DevOps organization. We have work upcoming to add this functionality for use with feeds in other organizations associated with your Azure Active Directory at a future date. Let us know if this is something you want for your group here!
We always appreciate your feedback, because it helps us prioritize what we should work on. If you have a new idea, change you’d like to see, or a suggestion on what you’d like to see next, here are some options:
- Review the existing suggestions on the Developer Community, and upvote for one that represents your thoughts
- Create a new suggestion if there are no existing ones that suit
- Reach out to us on Twitter at https://twitter.com/AzureDevOps