Sometimes we need to start several build steps in parallel for example run tests with specific criteria or upload/download dependancies

Consider options to reduce build time of hosted build agent significantly. I don't have problem paying for improved performance if there were such option.

For example dotnet restore build task takes 95 seconds for simple asp.net core 2 app in each build. Packages could be cached.

Agent initialization takes 39 seconds. Agent could be initialized in advance, why not?

In the new Team Foundation Build 2015 (https://msdn.microsoft.com/Library/vs/alm/Build/feature-overview) we can either add CI triggers that trigger a build with every check-in or we have the Scheduled triggers. It would be nice to have an option in the Scheduled Triggers that it only runs if there were changes since the last run (new ChangeSet).
We could use this since we build our Xamarin app with the new build server and publish it to the alpha track in the PlayStore, but we only want to do this once a day and only if there were changes since the last build.

In my on-prem TFS I can set the priotity of a queued build. I can't find this in VSTS. It would be helpful because sometimes I want to give my manual build more priority than the CI builds

Currently if we use "Auto-complete" option inside of pull request that has expired build. It will wait until that build is restarted manually and successfully completed. It would be nice if expired pull request build would started automatically when "Auto-complete" option is used.

You recently introduced Path Filters for vsts + git. It is not yet available for Github. Would be awesome if support could be added.

Submodules work in the new build system in TFS/VSTS 2015 however, they either need to come from repos in the same team project or from repos that are anonymously accessible.

This suggestion is split from "Add submodule support in Visual Studio Git Extension" (http://visualstudio.uservoice.com/forums/330519-team-services/suggestions/3606383-add-submodule-support-in-visual-studio-git-extensi)

This is a request to integrate TypeScript as a supported language for SonarQube.

This would be a way to integrate TSLint into Visual Studio, so that warnings are available on build.

Furthermore, SonarQube offers additional features, such as incremental technical debt analysis (i.e. "only warn when the code I write has errors - not for the whole solution"). This kind of analysis is useful for incrementally converting a solution.

Make it possible in VSTS to add Services (a.k.a. service endpoints) on the project collection instead of on individual projects only.

When you use the same service (e.g. an on-premise Octopus Deploy Server) in multiple VSTS projects you need to add a service endpoint to each project.
Managing this becomes a burden when you have lots of projects in VSTS

We are using the Publish Build Artifacts task and it is incredibly slow. We'd like to see this get faster.

https://www.visualstudio.com/en-us/docs/build/steps/utility/publish-build-artifacts

TFS Online should provide a way to set a time zone for the TFS server (or per collection).

You could even just implement it when setting Time Zone on https://***.visualstudio.com/_admin/_home/settings.

Most of the people in the world is not living in a place where UTC is the correct timezone.

This affects:
* TFS cases timestamps
* Runtime timing issues if you have integration tests with other servers (with correct time zone).
* Probably more...

Batch option is really useful, the way it worked VS2013 reduced the bottle necks when many change-sets were submitted. This is a very useful feature to continue.

We have a branch protected by polies (i.e. successful build and must have two reviewers).

It would be good to have an option on the branch pollicy to allow Auto-Complete to be the default option on new pull-requests

Some tasks have the textboxes that support multiple line content, such as Delete task, but multiple lines variable is not supported, it's better to support it.

Add "Build event if nothing has changed since previous build" to TFS 2015 scheduled build of new build system.

In the past weeks (from 9/6/2016) something changed in build code coverage reporting that strips the stylesheet tags in the head of code coverage reports. Previously, our reports generated with karma and istanbul were displaying perfectly with the included stylesheets. Now, the same coverage artifact displays without any of the included css styles. Looking at the frame source shows all the stylesheet tags stripped from the head section. I'm not sure which recent change in team services started removing this.

Currently it is possible to trigger a build when pushing commits to branches, but it is not possible to trigger a build when pushing tags.