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. Improve hosted build agent performance with build caches

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365799/improve-hosted-build-agent-performance-with-build.html
    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?

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

    We’ll send you updates on this idea

    56 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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 →
  3. Allow Import of pipeline for project with no pipelines.

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/366320/allow-import-of-pipeline-for-project-with-no-pipel.html
    When I enter a project with existing build pipelines, I get a menu on the left that I can import a template pipeline from. When there are no build pipelines created yet, this menu does not appear and I have to create an empty build pipeline, to then be able to access the menu to import my real build pipeline.

    Could you make it possible to import a build pipeline on a project where none exist yet.

    5 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. Provide option to "Disable" the Build/Release Definition in TFS/VSTS

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365947/provide-option-to-disable-the-buildrelease-definit.html
    Currently we don't have any option to disable the build/release definitions temporarily and leads to trigger the builds accidentally by developers which we don't want. We can recreate the build definition by deleting it but it not a good idea in this situation.
    Can you please provide an option to disable the build/release definition, and make it like the build should not be triggered by anyone until it is enabled by the administrator.

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

    We’ll send you updates on this idea

    8 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  5. Support wildcards (*) in Trigger > Path Filters

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/366363/support-wildcards-in-trigger-path-filters-1.html
    Would be great if we could use wildcards notation in Path Filters of Trigger options in Build. Here's a case study :

    Path Filter :
    Include | src/app/**/myapp*

    which would match :
    src/app/core/myapp
    src/app/core/test/myapp.test

    4 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 →
  6. Docker image cache on Hosted linux agent

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365988/docker-image-cache-on-hosted-linux-agent.html
    For Hosted VS 2017 agent, it caches some docker images (https://github.com/Microsoft/vsts-image-generation/blob/master/images/win/Vs2017-Server2016-Readme.md#docker-images), it's better to cache some images on Hosted linux agent.

    6 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 →
  7. Ability to leave comments/notes on Build/Release tasks

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/366096/ability-to-leave-commentsnotes-on-buildrelease-tas.html
    It would be nice to be able to leave notes or comments on build tasks if there is a tidbit of knowledge or something that you would like to leave in there for the next person to be able to read if they need more information about how/why that task is configured.

    2 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 →
  8. Rerun failed build task/step

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365697/rerun-failed-build-taskstep.html
    Provide a way/configuration people could be able to rerun some failed tasks server times in the build pipeline.

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

    We’ll send you updates on this idea

    21 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  9. Permissions to view Build Folders

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/366049/permissions-to-view-build-folders.html
    I am trying to hide a Build Definition folder. If I edit the permissions for a folder and set "View build definition" explicitly to Deny on Readers but then Allow for my target group, the build definitions themselves are now hidden. However, the folder itself is still visible. Is there any way to hide the folder itself? If not, please add a new permission for "View folder". It just seems confusing to show an empty folder to everybody, and if each team creates…

    4 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 →
  10. I really would like to use a Variable System.CollectionName instead of System.CollectionId in TF Builds

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/366309/i-really-would-like-to-use-a-variable-systemcollec.html
    I really would like to use a Variable System.CollectionName instead of System.CollectionId in TF Builds

    1 vote
    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 →
  11. 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 →
  12. Add Azure PowerShell task to agentless phase of VSTS build

    To allow starting of Azure Build Machine, add support for the Azure PowerShell task to the agentless phase of VSTS. The Azure Functions should work, but the current timeout of 20 seconds on function return, prohibits the starting of a virtual machines without build several functions and change them together. Needs to be simple.

    2 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. Allow TFS builds to update submodules with --remote

    In the build process, in the Get Sources step, it's currently possible to checkout submodules. However, they're stuck at whichever hash is commited to the main git repo.

    In practice, you run
    2018-03-15T21:49:23.1470756Z ##[command]git -c http.https://jet-tfs.visualstudio.com.extraheader="AUTHORIZATION: bearer ********" submodule update --init --force

    It would be nice to have the ability to check something off which adds --remote, allowing users to use the most recent commit to the branch specified in .gitmodules.

    2 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 →
  14. Publishing Build Artifacts is way too slow

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365656/publishing-build-artifacts-is-way-too-slow.html
    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

    59 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 →
  15. Show number of failed tests in email notification, not only percentage

    Currently the email notifications for builds with failed tests lists the percentage of passed tests (e.g. "(Build) Failed - 99.73% tests passed").

    I think it would be more useful to show the (absolute) number of failed tests, rather than the passed/failed percentage. There's nothing I can do with the percentage, but the exact number may tell me more - especially when practicing TDD.

    2 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. Build Agent Priority

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365620/build-agent-priority.html
    We currently have 3 on-prem build machines, with 4 build agents each.

    The priority to "grab" agents seems always to be in the order that they were installed (in our case we installed server by server), so if a Build uses 4 Agents, they all get used from the same server.

    For us, it would be faster if the build agents that get used for a single build would be spread across servers.

    So my suggestion is that you have the ability to…

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

    We’ll send you updates on this idea

    9 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  17. Support Git "***no-ci***" for pull request builds

    When commiting with a message containing the keyword "***no-ci***", the trigger if the build definition is skipped

    However, if there the branch is in a pull request, then there is no way to skip the build.
    It would be great if the Pull Request build would apply the no-ci keyword and be able to skip the build

    12 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. 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 →
  19. 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 →
  20. Scheduled builds - More flexible timing configuration

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365630/scheduled-builds-more-flexible-timing-configuratio.html
    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…

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

    We’ll send you updates on this idea

    12 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 37 38

Azure DevOps (formerly Visual Studio Team Services)

Feedback and Knowledge Base