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 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

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

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.

Provide a way/configuration people could be able to rerun some failed tasks server times in the build pipeline.

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

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)

Currently you can only use the hosted build if your build + repository is less than 10GB. Even with a shallow fetch our repository is near 10GB and then we run into issues while building.

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...

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.

As things stand currently, if someone deletes a build definition or a release definition there is no path to recovery short of restoring a backup. This isn't always possible especially given how quickly events move in TFS. Even restoring a TPC into a different environment can create problems. Given that recycle bins are now a feature in work items, I'd like to see this functionality extended to build definitions and release definitions....or at least if we can see who deleted a given definition that would be a welcome addition.

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.

The Azure File Copy build task provides a convenient way to copy your build output to Azure Blob Storage or an Azure VM. It would be useful to extend this to add the ability to copy files to Azure File Storage. This would seem plausible as the existing task uses AzCopy, which can be used to copy files to File Storage as well as Blob storage.

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.

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

The UI for defining time-based build triggers isn't flexible enough. It can only support fixed times on days of the week.
How about;
- Run a job on specifc day of the month (first, last, etc) - at a given time
- Run a job each hour, or two hours (can be done but would require adding 24 timings to the existing UI)
- Run job on day related timings - e.g. first Monday of month, last Wednesday

The CRON timing syntax is powerful (although admittedly hard to read/define)

We used to get notification from the tray of our windows machine for a finished build while using the xaml build definitions, it also had an option to reconcile workspace. The same functionality is not available for the vNext builds. We need a way to reconcile workspace for vNext build. More detail info please refer here：http://stackoverflow.com/questions/39344110/reconcile-workspace-for-tfs-2015-vnext-builds/39360344?noredirect=1#comment66107698_39360344

Moreover, there also has been a feature request for vnext build notification https://visualstudio.uservoice.com/forums/330519-team-services/suggestions/11081358-build-notifications-for-build-vnext .You can either vote up it.