Visual Studio Team Services Sprint 114 Delivers -- Visual Studio Magazine

Visual Studio Team Services Sprint 114 Delivers

Visual Studio Team Services team are in the midst of rolling out yet another sprint, this one with additional Delivery plans features, a more optimized mobile work item experience, and some other Team features.

By Michael Domingo
03/09/2017

For the Visual Studio team, Tuesday was pivotal, with a bunch of deliverables highlighted by the Visual Studio 2017 launch. Meanwhile, the Visual Studio Team Services folks continue plugging away in parallel and are in the midst of rolling out VSTS Sprint 114.

Microsoft's Brian Harry highlights in his blog a number of goodies in this sprint, including some progress on Delivery plans features, a more optimized mobile work item experience, and some other Team features.

Delivery plans have a small and new but important change that can be the difference between seeing changes having them go by unnoticed by the team. That small change comes in the form of a new Field Criteria feature that is embedded at the end of the Delivery plan boards. Field criteria are filterable, so that plans will appear on on calendars based on the criteria chosen on this board.

Another nifty feature is an update to the mobile discussion control that allows for submitting comments on a smartphone. The release notes emphasize that its addition to the sprint is for preview, so the team is looking for some feedback on its usability. One other usability feature of the mobile discussion control is the ability to filter, search and select users when assigning a work item from the control.

The My Pull Requests view now lists any pull requests for members assigned to multiple teams, which centralizes PRs. According to the release notes, this feature will be migrated to the Code tab.

For a complete list of features being rolled out in this sprint, see the release notes here; a roadmap of all the work the team plans to implement in upcoming sprints is here.

About the Author

Michael Domingo is a long-time software publishing veteran, having started up and managed several developer publications for the Clipper compiler, Microsoft Access, and Visual Basic. He's also managed IT pubs for 1105 Media, including Microsoft Certified Professional Magazine and Virtualization Review before landing his current gig as Visual Studio Magazine Editor in Chief. Besides his publishing life, he's a professional photographer, whose work can be found by Googling domingophoto.

Printable Format

comments powered by Disqus

Featured

Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.
Diving Deep into .NET MAUI

Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.
Copilot AI Boosts Abound in New VS Code v1.96

Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.
AdaBoost Regression Using C#

Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.
Versioning and Documenting ASP.NET Core Services

Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.