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. Being able to use the short commit ID to Build from previous commit

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365513/being-able-to-use-the-short-commit-id-to-build-fro.html
    On VSTS if you want to build from a previous GIT commit ID you have to provide the full hash of the commit.

    It would be nice to be able to use the short commit ID as the full commit ID is not easy to get from VSTS web interface or Visual Studio.

    41 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 →
  2. Reconcile Workspace for vNext Build

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365582/reconcile-workspace-for-vnext-build.html
    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.

    40 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 →
  3. Allow Build Agent Capabilities to be used through Environment Variables

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365520/allow-build-agent-capabilities-to-be-used-through.html
    My setup build definition (Team Build 2015) uses Dotfuscator so I created a user capability on my build agents named Dotfuscator with the path to the executable as a value.

    On machine A, dotfuscator is installed on the C:\ drive while on B it's installed on the D:\ drive.

    I would love to be able to use something like $env:CAPABILITY_DOTFUSCATOR in my Powershell script and have it resolve to the path I entered on my build agent instead of having to hack something…

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

    We’ll send you updates on this idea

    5 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  4. TFBuild 2015: Provide "Check in changes after successful build" option in TFVC

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365573/tfbuild-2015-provide-check-in-changes-after-succes.html
    When using a gated check in trigger it is sometimes necessary to trigger the build with non-default build variable values (Rebuild='true' instead of the default value 'false' for example).
    To change the build settings of a gated check in build there is a workaround in the old build system: Shelve your changes and trigger the build manually with the option: "Check in changes after successful build".

    In the new system you can trigger a build with a shelveset, but there is no option…

    36 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 →
  5. Optionally fail Visual Studio Test build step if no test assemblies were found or no tests were run

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365690/optionally-fail-visual-studio-test-build-step-if-n.html
    It would be great if there's options for the test step to fail if:

    - No test assemblies were found OR/AND
    - No tests were run

    This will ensure that when there's a configuration error or something in the source has changed, rendering the test filter invalid, the build fails instead of silently continuing.

    This is manageable by human checking of course, but since this would require verifying every important build, it seems logical to want to put that ensuring logic into the…

    35 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. Checkout/Build Multiple GIT Repos in a single TFS Build

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365607/checkoutbuild-multiple-git-repos-in-a-single-tfs-b.html
    We have a TFSVC repo which we're (trying) to move to GIT (using tfsgit) but a TFS build can only check out a single GIT repo. Our existing TSFVC build system simply checks out various parts of the tree which are required for the build, but these are logically independent repos so they need to be in independent GIT repos. I have resorted to using a powershell script to manually clone the GIT repos and then build - which is obviously a terrible…

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

    We’ll send you updates on this idea

    4 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  7. Allow Enable/Disable build (similar to XAML builds)

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365525/allow-enabledisable-build-similar-to-xaml-builds.html
    Allow us to enable/disable a build definition. There are times when we need to temporarily disable Triggered (CI / Scheduled) builds. Please allow a quick way to enable/disable an entire build definition.

    Currently, if we just remove the trigger, then it deletes all of the trigger settings and we have to recreate them each time.

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

    We’ll send you updates on this idea

    4 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  8. Using TFS 2015 Build (Build vNext) email alerts don't show associated check-ins

    I have a XAML Build Definition that is setup to trigger on every check-in. I also have email alerts setup for any time a build completes. With the XAML Build, it would show me the associated check-ins that were included in that build (user, notes, ID). I have setup a 2015 Build definition and I still get a completed build email, but it does not have any of the check-in information.

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

    We’ll send you updates on this idea

    5 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  9. Enable empty variable on Task Group

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365693/enable-empty-variable-on-task-group.html
    Right now it is not possible to use empty variable on task groups. It should be optional. If empty, use the default value defined on the task group (which could be empty too)

    Example

    Task group with build / test. I want to be able to specify Test filter criteria if I need to, but i may want to leave it blank

    using TFS 2017.2

    33 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. Add .NET 4.7.2 to Hosted VS2017 agent

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365964/add-net-472-to-hosted-vs2017-agent.html
    4.7.2. is not available on VSTS.

    "C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.targets(1098,5): Error MSB3644: The reference assemblies for framework ".NETFramework,Version=v4.7.2" were not found. To resolve this, install the SDK or Targeting Pack for this framework version or retarget your application to a version of the framework for which you have the SDK or Targeting Pack installed. Note that assemblies will be resolved from the Global Assembly Cache (GAC) and will be used in place of reference assemblies. Therefore your assembly may not be correctly targeted for…

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

    We’ll send you updates on this idea

    6 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  11. Using Variable in Solution Path in a Visual Studio Build Task

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365601/using-variable-in-solution-path-in-a-visual-studio.html
    I use a single build definition for many branches, but I have to edit the definition each time to point to the correct solution.
    For example, my solution path is $/repository/Development/branchName/name.sln. I want to define a variable and use it the the path like $/repository/Development/$(change)/name.sln and enter the variable value when queue build.

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

    We’ll send you updates on this idea

    7 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  12. fetch source from Git via SSH in Visual Studio Team Services

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365642/fetch-source-from-git-via-ssh-in-visual-studio-tea.html
    Fetching source from GIT via SSH feature is necessary if you must use SSH.

    28 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. "Publish Test Results" build step with failed tests should update build status

    In Build vNext, yf we are using custom scripts to run tests, and then we use the "Publish Test Results" build step to merge the results, they are probably displayed as passing or failing in the Test Results section of each build.
    Nevertheless the build status is still shown as Succeeded, instead of Partially Succeeded or even Failed.
    I'd like to have a way to mark the build as Partially Succeeded in the same way as if I was using the "Visual Studio Test" build step to run the tests.

    I see others had the same issue as shown here …

    28 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. Enable user defined variable in get sources step

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365692/enable-user-defined-variable-in-get-sources-step.html
    In Get Source step, you can choose the branch which list in the pick list. It will be more convenient if the branch name can be defined by a build variable.

    25 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 →
  15. Provide the capability to chain builds (one build calls another build definition)

    Please provide a means to trigger other build definitions and wait for their results (or build in parallel and then wait for all results)

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

    We’ll send you updates on this idea

    4 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  16. Allow build to use ssh authentication while checking out git sub modules

    Allow build to checkout sub modules linked using ssh path during build process.

    Scenario:
    I have a container repository which has a sub module linked using ssh pattern. e.g url = ssh://xx@xx.visualstudio.com:22/_git/xx

    I have "check out submodules" option selected in my build definition. But build cannot check out the sub module during the build as it fails in SSH authenticaion.

    Balamurali Sundaramoorthy

    24 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 →
  17. Use [ci skip] rather than ***NO_CI***

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365801/use-ci-skip-rather-than-no-ci.html
    Basically most of the others CI use [ci skip] or [skip ci] (e.g. Travis, CircleCI, Concourse)

    Some dependencies use [ci skip] as a pattern to skip automatically versioning from their CI, why not make VSTS also accept it?

    References:
    https://docs.travis-ci.com/user/customizing-the-build#Skipping-a-build
    https://circleci.com/docs/1.0/skip-a-build/
    https://github.com/concourse/git-resource#behavior

    23 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 →
  18. Link code coverage data from auto build results to pull requests

    Similar to https://visualstudio.uservoice.com/forums/330519-team-services/suggestions/13122975-show-coverage-inline-with-source-code

    But we wish to show the coverage in pull requests. This helps us prevent leaks in code coverage:

    Preffered environment:
    * VS Git repository with branch policy mandating pull requests
    * vNext Continous Integration build job configured to run automatically on pull requests
    * Code coverage enabled
    * Coverage would be rendered in the source diff gutter red(not)/green(full)/orange(partial)/grey(ignored)
    * Source in test project automatically excluded
    * Support for specifying excluding additional files or blocks, eg checked in generated files, certain namespaces, or auto properties

    Bonus points:
    * Summary for pull request (% coverage on new code)
    *…

    22 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 →
  19. TFS 2015 build vNext agent prioritization

    Add agent prioritization to vNext build engine.
    With many build servers deployed in given pool, we have different hardware power on most of them.
    It would be good to be able to run builds on fastest ones, and when busy fallback to weaker ones.

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

    We’ll send you updates on this idea

    5 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  20. Visualize YAML Builds

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365999/visualize-yaml-builds.html
    When YAML builds are used it does not visualize the steps that are defined in the YAML declaration.

    This is fine for the people whom have access to the file and know how that works but for the others it is an empty build without knowing what it does.

    It would be great to have the YAML file rendered and visualized in read-only mode so that it acts as living documentation.

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

Azure DevOps (formerly Visual Studio Team Services)

Feedback and Knowledge Base