Visual Studio Team Services

Welcome to the Visual Studio Team Services (VSTS) and Team Foundation Server (TFS) UserVoice site. This site is for suggestions and ideas for VSTS (cloud) and TFS (host yourself). You can also add suggestions for the Visual Studio IDE or Visual Studio Code. Or go to Developer Community to file a VSTS or TFS bug.

You might also be interested in our Features timeline to see what features are under development and which features we completed.
We also added an Announcements section where we will be posting special opportunities for you to participate in.

Read about current UserVoice statuses and their definitions in our article “What Does the Status of My Feedback Mean?” article.

We look forward to hearing from you!

The VSTS team
Terms of Service and Privacy Policy

How can we improve Visual Studio Team Services (VSTS)?

(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 pruning of a Git remote to the Team Explorer; something like right-click on the remote --> Prune. Stale branches are annoying.

    Add pruning of a Git remote to the Team Explorer; something like right-click on the remote --> Prune. Stale branches are annoying.

    32 votes
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)

      We’ll send you updates on this idea

      1 comment  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
    • Support displaying the svg image in markdown from webportal

      Currently, the svg image in markdown cannot be displayed correctly fron web portal if the svg image is hosted in TFVC/Git repositories.

      30 votes
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        I agree to the terms of service
        Signed in as (Sign out)

        We’ll send you updates on this idea

        4 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
      • View history for whole GIT repository.

        Currently in Visual Studio 2015 when looking at the branches tab for a GIT repository, I can do a history for any branch. The root of the GIT repository will show the history for the currently checked out branch. This can already be had looking at the history for the highlighted branch. It would be nice to have the history of the root of the repository show the history for all branches very much like the "Visualize All Branch History" available in git-gui by Shawn Pearce, et. al. in the windows git package suggested by Visual Studio.

        29 votes
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          I agree to the terms of service
          Signed in as (Sign out)

          We’ll send you updates on this idea

          0 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
        • 28 votes
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            I agree to the terms of service
            Signed in as (Sign out)

            We’ll send you updates on this idea

            5 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
          • Share single branch policy by multiple branches

            I would like to be able to define single branch policy shared by (applied to) multiple branches. Policy assignment to branches should be rule based similar to branch filters in continuous integration trigger.

            For example i would like to be able to assign same branch policy to all branches named refs/heads/release/*.

            27 votes
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              I agree to the terms of service
              Signed in as (Sign out)

              We’ll send you updates on this idea

              5 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
            • Ability to see labels in browser view / TFS Web Access

              There seems to be no way to view labels at all in the web access to TFS. Any plans to support it? Would be nice for us non-Visual Studio developers :)

              26 votes
              Sign in
              Check!
              (thinking…)
              Reset
              or sign in with
              • facebook
              • google
                Password icon
                I agree to the terms of service
                Signed in as (Sign out)

                We’ll send you updates on this idea

                2 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
              • Make cross-team project checkins properly respect checkin policies of each individual team project.

                It is currently possible to check in files that fail the checkin policies of a team project by also checking in files from other team projects at the same time. See http://connect.microsoft.com/VisualStudio/feedback/details/726309/custom-checkin-policy-not-being-applied for more details about this currently "by design" "feature".

                26 votes
                Sign in
                Check!
                (thinking…)
                Reset
                or sign in with
                • facebook
                • google
                  Password icon
                  I agree to the terms of service
                  Signed in as (Sign out)

                  We’ll send you updates on this idea

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

                  As explained in this blog post (http://blogs.msdn.com/b/visualstudioalm/archive/2015/10/08/how-we-use-user-voice-to-make-a-better-product.aspx), we had updated the status of this suggestion to “Under Review” to let you know we are tracking it on our backlog. To better indicate which one we are actively working on or which ones are on our 6-month plan, we introduced the states “Started” and “Planned”. The goal is to give an update on in progress suggestions at least every 3 months. This suggestion is still on our backlog, but they are not part of the 6-month plan.

                  Ewald Hofman

                • Revert all unchanged items from changeset before check-in

                  Imagine 100 checked-out files, while trying something out, and now you want to check-in your changes.
                  I feel more comfortable if I see directly which files really changed, before checking-in.

                  A button "Undo all unchanged" would e.g. undo 90 of these 100 files and now you see clearly which 10 files you really changed.

                  26 votes
                  Sign in
                  Check!
                  (thinking…)
                  Reset
                  or sign in with
                  • facebook
                  • google
                    Password icon
                    I agree to the terms of service
                    Signed in as (Sign out)

                    We’ll send you updates on this idea

                    4 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
                  • implement a more intelligent merge for xml files (including project files) and sln files

                    Merging project files and especially solution files is a real pain currently. For solution files, it would probably be better to ditch the current format altogether and replace it with a more sane xml format. The core problem is that projects are numbered, so when 2 users add a project to the solution, you have to either fix it by editing manually or disregard the changes and re-add your projects. It's a pain either way.

                    25 votes
                    Sign in
                    Check!
                    (thinking…)
                    Reset
                    or sign in with
                    • facebook
                    • google
                      Password icon
                      I agree to the terms of service
                      Signed in as (Sign out)

                      We’ll send you updates on this idea

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

                      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 to repositories in VSTS are either unparsable by Golang (the Git SSH paths) or require embedded authentication…

                      25 votes
                      Sign in
                      Check!
                      (thinking…)
                      Reset
                      or sign in with
                      • facebook
                      • google
                        Password icon
                        I agree to the terms of service
                        Signed in as (Sign out)

                        We’ll send you updates on this idea

                        1 comment  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
                      • Add Markdown support for source checkin/commit comments.

                        For displaying checkin/commit comments for either TFS Source or Git Source, I suggest you add Markdown support so that some simple formatting can be included in comments.

                        To get more details visit Markdown specs page http://daringfireball.net/projects/markdown/.

                        25 votes
                        Sign in
                        Check!
                        (thinking…)
                        Reset
                        or sign in with
                        • facebook
                        • google
                          Password icon
                          I agree to the terms of service
                          Signed in as (Sign out)

                          We’ll send you updates on this idea

                          2 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
                        • Allow proper git integration without ms-persist.xml

                          Although I welcome git integration in VS2013 and TFS, Microsoft have put in a strange and unnecessary proprietary extension; namely ms-persist.xml. This file is saved to the git repo, and is used so that users can select to "exclude" files in the "Changes" dialog in Visual Studio. I don't see the point in this. I'd rather work with Git's built-in staging area.

                          Why not provide an option to have full Git integration, and not use ms-persist.xml? When this option is selected, ms-persist.xml should not be written to or read from the Git repo dir. The Changes section would change to…

                          25 votes
                          Sign in
                          Check!
                          (thinking…)
                          Reset
                          or sign in with
                          • facebook
                          • google
                            Password icon
                            I agree to the terms of service
                            Signed in as (Sign out)

                            We’ll send you updates on this idea

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

                            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 happily fast forward.

                            We'd accept it falling back to a merge commit if other changes had been…

                            24 votes
                            Sign in
                            Check!
                            (thinking…)
                            Reset
                            or sign in with
                            • facebook
                            • google
                              Password icon
                              I agree to the terms of service
                              Signed in as (Sign out)

                              We’ll send you updates on this idea

                              3 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
                            • Syntax highlighting for Scala, bash (and other things) in VSO text viewer

                              A bunch of languages/file types we are using have no syntax highlighting in VSO text viewer:

                              - Scala (.scala, .sbt)
                              - .properties
                              - bash (.sh, .profile, .bashrc)

                              Ideally would be nice to have parity with GitHub in this area, but probably can start with these three?

                              24 votes
                              Sign in
                              Check!
                              (thinking…)
                              Reset
                              or sign in with
                              • facebook
                              • google
                                Password icon
                                I agree to the terms of service
                                Signed in as (Sign out)

                                We’ll send you updates on this idea

                                2 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
                              • Support github flavored markdown

                                GitHub uses GitHub flavored markdown. VSTS evidently uses Markdown basic and you get a different and better rendering experience on GitHub. Please consider using the same rendering engine for VSTS.

                                24 votes
                                Sign in
                                Check!
                                (thinking…)
                                Reset
                                or sign in with
                                • facebook
                                • google
                                  Password icon
                                  I agree to the terms of service
                                  Signed in as (Sign out)

                                  We’ll send you updates on this idea

                                  4 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
                                • Code Review Notification

                                  I find it to be a flaw when someone on my developer team has to send me a message on Skype telling me they have sent me a code review and then I have to go dig through "My Work" to find the review and accept it.

                                  What I would like to start seeing for this and other events like this that occur in Visual Studio would be "Skype-like notifications" that happen perhaps on the bottom right hand side of my screen, a little box that pops up that tells me I have a new code review. I could then…

                                  23 votes
                                  Sign in
                                  Check!
                                  (thinking…)
                                  Reset
                                  or sign in with
                                  • facebook
                                  • google
                                    Password icon
                                    I agree to the terms of service
                                    Signed in as (Sign out)

                                    We’ll send you updates on this idea

                                    2 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
                                  • Quick code editing switch or warning

                                    The quick editing feature from TFS2015 doesn't take into consideration the check-in policies that are in-place for a team project.

                                    Scenario:
                                    Work item policy setup in order to warn the developers to associate their changesets with one or more work items. They can bypass the policy but at least they're aware of it.
                                    If they check-in from web interface then they are not even aware that a check-in policy exits.

                                    It would be useful if a setting would be provided to enable/disable this feature. Or an warming that would notify the users that a check-in policy is in place when…

                                    22 votes
                                    Sign in
                                    Check!
                                    (thinking…)
                                    Reset
                                    or sign in with
                                    • facebook
                                    • google
                                      Password icon
                                      I agree to the terms of service
                                      Signed in as (Sign out)

                                      We’ll send you updates on this idea

                                      7 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
                                    • Add iteration support to Pull Request

                                      When a new PR is created, it is clear the developer waits for review. Then after first review, if reviewer is "Waiting", it is now clear the reviewer is waiting for new commits from the developer. But after that things get messy, because it is not clear whether the reviewer is still waiting for the developer to address his comments, or the developer is waiting for his new code to be reviewed.

                                      Since code review is an iterative process, it would be great if PR would also support iterations:
                                      1. It should always be clear who is waiting for whom.…

                                      22 votes
                                      Sign in
                                      Check!
                                      (thinking…)
                                      Reset
                                      or sign in with
                                      • facebook
                                      • google
                                        Password icon
                                        I agree to the terms of service
                                        Signed in as (Sign out)

                                        We’ll send you updates on this idea

                                        2 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
                                      • Keep a pull request comment's context when code changes are pushed

                                        When I create a pull request, other team members can comment on specific lines of changed files to indicate things that should be addressed. After I push my changes, the code is updated, but the comments stay attached to the same line numbers, which might no longer be relevant. An example is attached.

                                        It would be better if the comments moved to the appropriate line when a change is made, or if the commit that the comment was originally made on could be shown easily. As of now, you have to guess what part of the code the comment was…

                                        21 votes
                                        Sign in
                                        Check!
                                        (thinking…)
                                        Reset
                                        or sign in with
                                        • facebook
                                        • google
                                          Password icon
                                          I agree to the terms of service
                                          Signed in as (Sign out)

                                          We’ll send you updates on this idea

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

                                          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.

                                          21 votes
                                          Sign in
                                          Check!
                                          (thinking…)
                                          Reset
                                          or sign in with
                                          • facebook
                                          • google
                                            Password icon
                                            I agree to the terms of service
                                            Signed in as (Sign out)

                                            We’ll send you updates on this idea

                                            4 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
                                          • Don't see your idea?

                                          Feedback and Knowledge Base