Sprint Planning Tweaks Added to Visual Studio Online Sprint 87

Along with Sprint 87 release, a user name anomaly in Visual Studio Code that affects developers on Windows machine is also fixed.

It's been a few weeks since the general release of Visual Studio 2015, but the wheels of progress continue to turn in other areas. Take Visual Studio Online, which is beholden to its own schedule of incremental improvement, with releases mainly tied to a monthly cycle, with more significant changes released as soon as the code is baked.

Just released was VSO Sprint 87, with a number of incremental improvements this time out. A post from Microsoft Program Manager Aaron Bjork runs down the highlights:

  • Rename columns in place: In the Kanban boards, columns can be renamed in place rather than having to shift to a configuration dialog. Adding, ordering, and deleting columns will be coming next, writes Bjork.
  • Capacity planning: Two buttons have been added to the Capacity tab that allow adding internal and external team members to a sprint plan.
  • Burndown chart: Addition of two lines, one showing how work on a sprint is progressing, and another showing what 's ideal. The lines take into account information on sprint member availability.

Bjork also highlights the work that the team has put into integrating the SonarQube code inspector into MSBuild, VSO and Team Foundation Server. In Sprint 87, the ability to perform a code quality inspection with SonarQube is specfically integrated into MSBuild as a build task, so now you can publish the results of builds.

Then there's Visual Studio Code, currently in development, with an updated preview release on the wire just a few days old that came with a number of documentation and language improvements. Soon after that release, another update was released, dubbed Recovery Update 0.7.10 for Windows, which fixed a truly vexing problem in which users starting VS Code after the 0.7.0 update saw just an open window, without any of the expected VS Code interface popping up.

"Shortly after making the 0.7.0 available we received bug reports and tweets about Code not coming up after the update," wrote Visual Studio Code Team Member Chris Dias, in a blog post. After failing to replicate the issue causing the empty window problem, a user alerted them to the issue having to do with non-ASCII characters used as part of a user name. The problem existed only on Windows systems, thus the Windows-only update.

To keep up on the feature improvements that the Visual Studio team is making on each project, check out the feature timeline here.

About the Author

You Tell 'Em, Readers: If you've read this far, know that Michael Domingo, Visual Studio Magazine Editor in Chief, is here to serve you, dear readers, and wants to get you the information you so richly deserve. What news, content, topics, issues do you want to see covered in Visual Studio Magazine? He's listening at [email protected].

comments powered by Disqus


Subscribe on YouTube