Azure DevOps (formerly Visual Studio Team Services)

Announcement: Last fall, we migrated this forum to Developer Community to provide you one convenient and responsive system for all feedback. As the final step in the migration, this forum will be closed off completely on June 1st, 2019. We encourage you to visit Azure DevOps Developer Community where you can now suggest new ideas, browse and vote on existing ideas, and engage with Azure DevOps teams

We’d like your suggestions and ideas to help us continuously improve future releases of Azure DevOps and Team Foundation Server (TFS), so we’ve partnered with UserVoice, a third-party service, to collect your feedback. Please do not send any novel or patentable ideas, copyrighted materials, samples or demos for which you do not want to grant a license to Microsoft.

This site is for feature suggestions; if you need to file a bug, you can visit our Developer Community website to get started.

Note: your use of the portal and your submission is subject to the UserVoice Terms of Service & Privacy Policy and license terms.

We look forward to hearing from you!
- The VSTS Team

How can we improve Azure DevOps?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Customize columns on TFS build history page

    In TFS build history page, It only shows columns like Name, Build Definition, Source Branch. Could it be customized to add other columns like "environment variables/build variables ".

    16 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    10 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  2. Support localdb for Team Foundation Service unit test runs

    It appears that unit tests against a database used to be supported (http://lateralcoding.com/unit-testing-ef-on-microsofts-new-team-foundation-service/), however, it appears that it is no longer.

    When I attempt to run a unit test that goes against localdb (e.g. with connection string "Data Source=(localdb)\v11.0; Initial Catalog=MyTest; Integrated Security=True", Team Foundation Service yields the error:

    System.Data.SqlClient.SqlException: System.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 52 - Unable…

    16 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  3. Enable Build Expiration for Manually triggered build policy in PR

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/366032/enable-build-expiration-for-manually-triggered-bui.html
    When setting a Build Validation Policy for a branch, the option for Build Expiration is disabled when the Trigger is set to Manual.

    Allow Manually triggered builds to expire when new code changes are pushed to the source branch within an open Pull Request.

    15 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  4. Force rebase to the latest commit in the target branch to complete the PR

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365890/force-rebase-to-the-latest-commit-in-the-target-br.html
    Like in github, have the option to not allow a PR to complete unless its commits are rebased on the latest version of the target branch

    15 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  5. Restore from multiple hosted feeds

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365848/restore-from-multiple-hosted-feeds.html
    In het NuGet task (v2.0) you can only select one hosted VSTS nuget feed when the option 'Feed(s) I select here'. There is an option to include nuget.org but it would be nice if you could select multiple (two or three) VSTS feeds.

    As suggested in the developer community (https://developercommunity.visualstudio.com/content/problem/110177/nuget-task-doesnt-allow-multiple-package-sources.html) it is possible to restore from multiple feeds by adding more restore steps. Unfortunately this only works by checking ' continue on error' at the first restore step(s). This is because…

    15 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  6. GVFS support for "Get source" build task

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365835/gvfs-support-for-get-source-build-task.html
    GVFS support can significantly speed up CI build time for large projects with a lot of assets.

    15 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  7. Specify values for variable per Schedule of Build Definition

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365812/specify-values-for-variable-per-schedule-of-build.html
    It would be great to allow to specfiy values of variables per schedule of a build definition.

    Motivation: The same build definition can be used as CI/Pull-Request and scheduled build (e.g. nightly build) with different options without the need to clone and modify the build definition.

    One use case is to execute only BasicCoverage-Tests within CI/Pull-Request builds and all Tests within the scheduled build.

    15 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  8. Allow Setting Build Variables in Pull Requests

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365725/allow-setting-build-variables-in-pull-requests.html
    Allow for the setting of build variables from the "New Pull Request Screen" to enable conditional build tasks

    When working with very large projects, SonarQube builds can take an extremely long time to build. Sometimes you may want to perform the SonarQube analysis on a pull request, and at other times you may not. I propose that VSTS add the ability to set build variables from a PR that can then be used to conditionally enable specific tasks in a build.

    15 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  9. Run VSTS build/release definitions locally

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365712/run-vsts-buildrelease-definitions-locally.html
    Please provide a local task runner to execute build and release definitions locally from Visual Studio on the local maschine. It would be a large advantage for the developers and other people to reuse e.g. the build definition also locally before submitting the source code.

    15 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  10. Build Notifications Should Include Associated Changes

    The end user should have the ability to select whether they want to include the associated work items and/or changes in the email.

    It is a lot more convenient to the developer to see the changes in the email, instead of having to log into TFS.

    15 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  11. vNext Build: Add options to the repository tab to set the same workspace options that VS offers

    As a build engineer, I'd like to be able to set advanced options on the workspaces TFS vNext Build agents create. This includes the ability to set the "File Time" parameter, and the ability to change the "Location" between Local or Server. I'd also like the ability to name the workspace, to better manage them as a TFS Administrator.

    Currently my experiences with vNext Build using TFS 2015 Update 1 only allow me to set the mappings. The agent auto creates a workspace with a name that cannot be changed via the build interface, and my options are limited to…

    15 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  12. Allow TFVC build definitions to target a specific VSO branch, and display branch during build

    Allow TFVC build definitions to target a specific VSO branch, and display branch targeted, and most recent changeset in target, on the build history.

    This capability is already made available for Git repositories in VSO - it would be extremely helpful to be able to target a specific TFVC branch for a build within the definition, and show which changeset is latest for that branch build.

    Currently, our workaround is to create the definition to point to a branch-specific solution file, and deploy build results using GruntTasks, but it doesn't show which changesets are included in that branch build.

    15 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  13. save the last used date filter in Build Explorer

    either allow users to set the default date filter or save the last used date filter in the Build Explorer.

    I never want to see builds just for Today (as is the default), nor do I want to see build older than 30 day. Since we retain 10ish builds, I don't thing defaulting to 30 days (or 28 that is available now) would be out of line.

    15 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  14. VSTS Hosted Agent with Windows Server 1803

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/366075/vsts-hosted-agent-with-windows-server-1803.html
    We currently have to use private agents to build Docker containers based on Windows Server Core 1803. Could you create a hosted agent pool which uses Windows Server 1803??

    14 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  15. Restore the Release button on the Build Results page

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365985/restore-the-release-button-on-the-build-results-pa.html
    When enabling the new build result page feature, it is no longer possible to deploy directly from a build result page.

    On the current (old) page, you get a "release" button once the build completes, which triggers the corresponding release definition linked via build artificats. This button is not present on the new build result page, which forces us to go through the Releases section, create a new release and find the correct build artifact, which is totally not intuitive.

    Please put back…

    14 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  16. Allow editing of YAML CI Builds through the GUI

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365951/allow-editing-of-yaml-ci-builds-through-the-gui.html
    Being able to update YAML builds via the gui would then just save them back to the git repository when saved (there is already UI that pops up when you save that could be used to set a commit message instead)

    You then get all of the benefits of having a YAML file stored in the gui with all the benefits of the low learning curve that the gui interface gives you. Would be a key differentiation point to many other CI systems.

    14 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  17. Prevent parallel execution of the same build definition

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365730/prevent-parallel-execution-of-the-same-build-defin.html
    I have build definitions that access some global external state. If it runs in parallel, the two runs will interfere.

    Therefore, I would like to have a "prevent this build definition from running in parallel with itself" checkbox, to ensure that only one agent is running it at the same time.

    14 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  18. Build priority as part of build definition

    When you start a build manually, you can set a pririty for your build.

    It would be nice if the build definition contained a default build priority, so that we could have our CI production builds have higher priority than the CI Development builds.

    Also when a check-in triggers several builds, it would be nice to have the option of prioritizing which ones are built first.

    Some of our feature branch builds can easily wait if we add a hotfix build in the build queue...

    14 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  19. Fail build on insufficient code coverage

    Please make it easier to fail the build if the code coverage is lower then a given %.

    The community and MS itself focus more and more on the code quality (see the checkin-policies for code-reviews etc.) but a basic indication for failing quality as low code coverage from unittests isn't a trigger to fail a build.

    To accomplish this we now have to edit the build-template or create our own build task.

    I think this is a relative small efford for MS and a huge help for the community to develop better unit tests and better code.

    14 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  20. Make the path selector field larger

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365808/make-the-path-selector-field-larger.html
    In the build definition editor: when you choose the path for the triggers the field is too small for a decent selection; if the path is too long you don't see the entire path; you have to wait for the tooltip which is very annoying if you 20 different paths to select so we have to use the REAT API to set/edit the paths.

    On the right side there's a lot of unused space.

    13 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →

Azure DevOps (formerly Visual Studio Team Services)

Feedback and Knowledge Base