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. VSTS Group Test Results by Namespace/Class

    In Visual Studio 2015 Test Explorer and in ReSharper there is an ability to group tests by Namespace/Classes. It would be nice to have the same sort of grouping option in the TFS/VSTS test results pane when reviewing a build. Currently you can group by container, but this doesn't show the hierarchy of tests.

    21 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 →
  2. Build Minutes Front and Center (Improve Build Notifications)

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365816/build-minutes-front-and-center-improve-build-notif.html
    Srsly.... we're running builds and they cost us money. Seems like this very important detail would be front and center for every notification sent to us. Please make the build minutes VERY CLEAR AND READILY AVAILABLE to your paying customers, so they don't have to go mucking around in your portal to see what sort of state our services are in, and/or worse yet, having a "ticking timebomb of death" feeling that's constantly hovering over our usage!!

    User experience (and sentiment), team. Very…

    20 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 →
  3. Build vNext ignore "no appropriate mapping" for shelf builds

    When building a shelveset, please ignore "No appropriate mapping exists for {PATH}" errors. If a mapping doesn't exist for that build, just ignore it. please. please just ignore it. don't fail the build. just move on.

    20 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. Make "sync sources" optional for each job

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365998/make-sync-sources-optional-for-each-job.html
    We want to create a build definition that allows us to build the project with corresponding UI tests on a dedicated build server and then distribute the generated build artifacts to a number of test servers, executing the UI tests.
    This works great with the concept of Jobs, but it's a little annoying that each job will download the source files from the repository even though they're not needed for the test process.

    Please make "sync sources" optional for each job, or even…

    19 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 →
  5. Preserve build information in Found/Integrated in build links

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365886/preserve-build-information-in-foundintegrated-in-b.html
    Hi,

    Build information for builds linked to work items using the 'Found in build'/'Integrated in build' link types are no longer available if the build was deleted.
    The only available information is the build id, which is pretty much useless to end-user.

    While I understand why this happens, I don't agree with it.

    Knowing in which version a bug was found and in which version it was fixed/integrated is crucial to almost everyone (QA, developers and product owners). TFS should reliably preserve this…

    19 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 →
  6. Select private build agents in Round Robin or Random order

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365703/select-private-build-agents-in-round-robin-or-rand.html
    At present, the agents in a queue are selected in a way such that the first agent always gets the maximum load. That is, the second agent gets the job, only of first is bust already. And third gets the job, if both first and second are busy.

    These has some disadvantages:
    1. Since 2nd and 3rd agents don't get much builds, they are usually not synced to the latest state of the repo. So when they do finally get a build, the…

    19 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 →
  7. Can we have a drop down choose-list / checkbox to specify a value to a variable ?

    When queue/trigger a new build, Can we have a drop down choose-list / checkbox to specify a given value (it is one in a existed value list) to a variable ? it can avoid some typo /fat finger issue for some given values and repeating type for each triggered build.

    19 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 variables in variable groups to be settable at build time

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365804/allow-variables-in-variable-groups-to-be-settable.html
    Ordinary Build variables have an option which allows them to be set a queue/build time. Variables in a variable group does not have this option.

    To get around it we currently define a variable on the build it self which refers the variable group variable, and then we allow this to be overridden at build time - it is not very intuitive and hard to maintain.

    18 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 →
  9. Azure Container Instance as Build Agent

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365717/azure-container-instance-as-build-agent.html
    With the upcoming release of Azure Container Instances (https://azure.microsoft.com/en-us/services/container-instances/), please add the ability to specify a container image to be used as a Team Services Build Agent that is automatically provisioned and destroyed for each build.

    18 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. more flexible wildcard used in branch filter (triggers in build definition)

    It will be more flexible if branch filter support the pattern like this (wildchard not only used at the end): *1/*, so that it can match branches like ft1/a, TF1/a, Ft1/a, fT1/a, ft1/b etc.

    18 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 →
  11. Add Compass / Ruby to the build capabilities of the hosted build agent

    We are currently reviewing the the vNext build process within Visual Studio Online.

    IT is great that we can use NPM / Grunt / Gulp etc, but is seems a short coming that we are not able to use compass to do the SASS compilation along with its other features.

    Thanks

    18 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 →
  12. Enable Continuous Integration Path Filters for Bitbucket

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365815/enable-continuous-integration-path-filters-for-bit.html
    Bitbucket CI integration does not currently support Path Filters. Please add this functionality. Why does a VSTS Repo only have this option? surely it could be ported to Bitbucket and other Repos that are supported?

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

    We’ll send you updates on this idea

    planned  ·  1 comment  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  13. Pipeline as code

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365687/pipeline-as-code.html
    Teams are pushing for automation across their environments, including their development infrastructure.

    Pipelines as code is defining the deployment pipeline through code instead of configuring a running CI/CD tool.

    17 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. Trigger build with variables

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365670/trigger-build-with-variables.html
    I don't know if we are the only one's who missnig this so throwing it out here to see.

    First off, we have a solution with multiple project that we are packing to NuGet. I have created a generic CI build definition for these where you input the project name as variable.

    The problem now is that we have to duplicate this definition for each project to be built and packaged and input the project name as variable. This also means that if…

    17 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. Add deleted builds option in the builds REST API query

    The old TFS .NET API has support for querying deleted builds.

    The new REST API no longer has that functionality. It would be very appreciated if you could add that option.

    More details here: http://stackoverflow.com/questions/37195274/cannot-access-deleted-builds-using-the-tfs-2015-rest-api

    17 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 →
  16. Bring back warning and error count on vNext build summary

    Include the number of warnings and errors in the build summary for vNext builds.

    With xaml builds, the summary showed "x error(s), x warnings", then the first several warnings and/or errors. If there were a large number, a notice that it was only a partial list would be shown. This was good because developers could see whether the count went up or down compared to other builds.

    On the other hand, vNext builds just show a partial list of warnings/errors, no counts, and no indication if you are seeing all of them or just a partial list. This means the…

    17 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 →
  17. Allow us to update an existing Secure File instead of having to delete and re-upload

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365861/allow-us-to-update-an-existing-secure-file-instead.html
    We have multiple iOS build definitions that use the same Provisioning profile for internal testers. Whenever we add a new device to the provisioning profile, we have to update the profile on VSTS under Secure Files, which is fine, but since there's no update feature for Secure files, I have to go to each build definition and update the provisioning profile used, even though the name of the file is the same as the out of date profile I deleted.

    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 →
  18. Scala and SBT builder

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365844/scala-and-sbt-builder.html
    Can you add support to build SCALA \ SBT ?

    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 →
  19. vNext Build variables and Queue new build UI

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365728/vnext-build-variables-and-queue-new-build-ui.html
    Currently all variables type is string.
    In addition, the 'Queue new build' dialog which is too small and not expandable, if ones want to set a variable with a list of values - the values should be added as a long comma separated string - Not comfortable, error prone and really not user friendly.

    suggestions:
    1) In the 'Variables' hub, supply a "variable type" next to each new variable + allowed values (if required)
    Example: A Radio button variable, Dropdown list variable
    Practical…

    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 →
  20. Visual Studio Test task show standard output in VSTS build log

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365663/visual-studio-test-task-show-standard-output-in-vs.html
    When queuing a build, for the visual studio test task, it only show the standard output message in log if the the test failed. But if the test passed, the standard output won't show in logs, we can only find related information in .trx file.

    It will be great if the output message can be displayed no matter the test result is pass or fail. Just like test in VS, it shows the output even the test is passed.

    16 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