Azure DevOps (formerly Visual Studio Team Services)

Announcement: This forum has been migrated to provide you one convenient and responsive system for all feedback. You can now suggest new ideas, browse and vote on existing ideas in the Azure DevOps Developer Community. To learn more about the migration please check out the release blog post

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. Add Git pre-receive hooks

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365841/add-git-pre-receive-hooks.html
    Add built-in Git pre-receive hooks to block undesirable commits from the repository. Examples include commit messages, file content scanning, and file names.

    135 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    16 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
  2. Migrate a shelveset to a different branch

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/366130/migrate-a-shelveset-to-a-different-branch.html
    Restore functionality in TFS/TFVC 2017 to migrate a shelveset to a different branch when unshelving.

    This functionality was available in Powertools 2015 via

    tfpt unshelve /migrate /source:"$/ProjectName/Branch" /target:"$/ProjectName/Targetbranch" "My Shelveset Name"

    But there is no equivalent or workaround for vs 2017 as far as I can tell.

    (https://stackoverflow.com/questions/49371144/visual-studio-2017-cannot-move-shelveset-to-another-branch)

    Moving incomplete work between branches as release dates change, or new work comes in is a common practice for us.
    Now we have to temporarily commit incomplete/broken work to merge it into other…

    20 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
  3. Use dropdowns in variables of vNext build definitions

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365862/use-dropdowns-in-variables-of-vnext-build-definiti.html
    Make it possible that use dropdowns in variables of vNext build definitions in TFS.

    Original post:
    https://stackoverflow.com/questions/48279008/use-enumerations-dropdowns-in-variables-of-vnext-build-definitions-tfs

    59 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
  4. Restore "Missing" TFS Power Tools functionality in VS/TFS 2017

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365649/restore-missing-tfs-power-tools-functionality-in-v.html
    With the removal TFS Power Tools for the 2017 release there are some significant features absent from Visual Studio 2017.

    Find by status (server workspaces) allowing you to search for a users checkouts.

    On the command line: online, scorch and treeclean don't appear to have any equivalents. These commands are very useful when automating the import/export of objects to or from TFS.

    429 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    85 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →

    For the Find by Status feature, we’re working on an extension to add this capability back to VS. We don’t yet have an ETA for the availability, but I’ll update here when it’s ready.

    For tfpt online, scorch, and treeclean, the functionality has been replaced by tf reconcile. If you use tfpt {command} /help, you’ll see a message about the specific options to use to get equivalent functionality with tf reconcile.

    Tfpt uu doesn’t have a replacement in tf.exe. The old tfpt commands should continue to work against newer versions of TFS and VSTS.

    Thanks,
    Matt Mitrik
    Program Manager | VSTS

  5. pull request diff ignore whitespace

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365666/pull-request-diff-ignore-whitespace.html
    When comparing pull request changes, could the whitespace be ignored in the file diff tab.

    110 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    21 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →

    We’re starting to take a look at this feature, and have some questions about exactly what people are expecting from this suggestion.

    Currently, the pull-request diff experiences ignore leading and trailing whitespace by default. For example, if only the indentation of a line changed, that line will not be highlighted as having any changes. This leads us to believe that this suggestion is about some other whitespace diffing behavior.

    We have some ideas about what this might mean, but we want to hear from our users. If you have any insights you wish to share to help us better understand this suggestion, please reply to this email and let us know.

    Thank you!

  6. Have branch police template to store the branch policies usually set for most branches

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365824/have-branch-police-template-to-store-the-branch-po.html
    It will be great that VSTS has branch police template that can store the branch policies users usually set for multiple branches and repos.

    This feature is more required that there have amount of branches/repos need to have the same branch polices.

    28 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
  7. Option to allow Auto-Complete to be the default option on new pull-requests

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365686/option-to-allow-auto-complete-to-be-the-default-op.html
    We have a branch protected by polies (i.e. successful build and must have two reviewers).

    It would be good to have an option on the branch pollicy to allow Auto-Complete to be the default option on new pull-requests

    76 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    23 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
  8. Change default title for pull request commits to not include PR id

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365716/change-default-title-for-pull-request-commits-to-n-1.html
    Right now, all pull requests generate a commit message that starts with "Merged PR: XYZ". That creates a cluttered commit history for the branch. It is more important to see the description of the changes made than what PR number was used. The PR number should go in the description of the commit if desired.
    There should be a way to change the pattern for the default generated commit message for a Git repo in VSO.

    71 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    9 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
  9. Can we please have syntax highlighting for pull request code?

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365740/can-we-please-have-syntax-highlighting-for-pull-re.html
    Could we please have better highlighting for common languages?

    53 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    11 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
  10. Pull Request list - add an option to be able to default to the "Active" list of Pull Requests instead of "Mine"

    In our organization, it would be more useful to default to the "Active" list of Pull Requests instead of to the list of "Mine" pull requests.

    It would be nice if there was a per-user preference that could be set to default to that tab instead.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
  11. When you browse to a Git Repo, the README.md file should be the first thing shown

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365892/when-you-browse-to-a-git-repo-the-readmemd-file-sh.html
    When you browse to a Git repo, like myproject.visualstudio.com/MyProject/_git/MyRepo, it shows a list of files in master, rather than showing README.md.
    It should show README.md.

    8 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
  12. Set version control permissions by REST API

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365828/set-version-control-permissions-by-rest-api.html
    Now we can set version control permissions through the VSTS web page https://account.visualstudio.com/project/_admin/_versioncontrol as the document https://docs.microsoft.com/en-us/vsts/security/set-git-tfvc-repository-permissions mentions.

    It will be convenient if we can also set version control permissions through REST API.

    21 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
  13. failed to start ssh session unable to exchange encryption keys - visual studio mac

    Hi,

    Trying do a checkout in VS Mac by configuring Git Repo using SSH protocol. Am getting the following error. If I do the same in command line, I am able to do a git clone.

    "failed to start ssh session unable to exchange encryption keys"

    5 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
  14. Add Golang support to VSTS Git

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365722/add-golang-support-to-vsts-git.html
    Over the past few years we at Yammer have been adopting Golang into our DevOps story and have found tremendous results. Previously we had been hosting all of our codebase on an internal Github Enterprise server. Now, however, we are migrating all of our code base and process up to Visual Studio Team Services.

    We ran into a snag though involving Golang imports. Full details on the issue can be found here: http://ppanyukov.github.io/2017/02/01/golang-with-vsts-repos.html

    The short of it is that the URL's for talking…

    52 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
  15. Enable fastforward merge from pullrequest

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365639/enable-fastforward-merge-from-pullrequest.html
    The opposite of https://visualstudio.uservoice.com/forums/330519-team-services/suggestions/6073200-no-fastforward-merge-from-pullrequest really.

    We'd like an option to allow fast-forward merges for Pull Requests (and even one step further, to automatically rebase the pull request off the destination branch).

    We end up merging small changes via Pull Requests (due to branch policies) and this can lead to the number of merge commits getting in the way of the actual commits for no real reason. Our developers rebase off master before creating the PR, so 90% of the time the merge will…

    166 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    22 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
  16. Drag and drop LFS files into web gui

    Using TFS on prem, with a git repository that has LFS configured in .gitattributes, we should be able to drag and drop a file that is configured for LFS in through the web GUI and that file should get a LFS pointer, and not the file as is.

    Our BI developers who work on our crystal report files do not need our entire repository cloned locally to work on their files nor should they need to have all of the git tools installed (and knowledge that is required to work them) to work with these files. Using the web gui…

    3 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
  17. Automatically start expired pull request build on "Auto-complete"

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365605/automatically-start-expired-pull-request-build-on.html
    Currently if we use "Auto-complete" option inside of pull request that has expired build. It will wait until that build is restarted manually and successfully completed. It would be nice if expired pull request build would started automatically when "Auto-complete" option is used.

    363 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    13 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
  18. Verify commits

    Validate commits and show verified commits in the UI (similar to what GitHub does).

    Git already supports this as seen here https://git-scm.com/book/en/v2/Git-Tools-Signing-Your-Work

    7 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
  19. Default destination project and repository in forked repository pull requests should be the forked project's master

    We have a template repository that we fork to multiple new projects. We then branch and pull request within those new projects/repositories as normal. Unfortunately, the VSTS UI defaults pull requests "into" the source repository when operating within a forked project. We'd like it to default to the forked repository.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
  20. Add a permission that not allow adding users in TFS

    As we know, Edit team project level permission defines the user management for the Project Administrators, but I want to have all abilities of Edit team project level permission except adding users. Please have a single permission that restrict adding users.

    3 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 44 45

Azure DevOps (formerly Visual Studio Team Services)

Feedback and Knowledge Base