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. Allow users to manually perform garbage collection ("git gc") against a visualstudio.com repo

    If you accidentally commit large packages to git, then delete them, the packages stay in the repository taking up space. It's possible to delete these packages from the whole history with the "git filter-branch" command, which dereferences the packages blobs. But to free the space the git garbage collector "git gc" needs to be run.

    Please allow users to either force a "git gc" on the remote visualstudio.com repository or to lower the threashhold for automatic garbage collection (by default this is 6700 objects I believe)

    43 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 →
    • Code review the changes for a task

      We follow agile and we check in frequently. We create tasks that spans from a day to 3 days. Once the task is completed by the developer it is sent for review. So we have multiple changesets to review. It is very hard to have a good picture of the changes to a file since the changes are across multiple changesets. As of now, we are finding all the files that are affected by that task and go to "view history" of the file and pick the most recent version and the version before the task started to get a…

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

        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

      • Connect by relation a code review to the changeset it was requested for (when doing review after checkin)

        As of today, when you do a code review before checkin, the code review is linked to the final checkin. However, if you initiate a review post checkin, the changeset is not updated with a link to the code review.
        This makes it impractical to overview what tasks and changesets that have been code reviewed in a post checkin scenario.

        40 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

          6 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
        • Support pull requests from different repositories

          So, our company is split. Product development and projects. Recently the product team wanted to deploy the new TFS git features to use a PR based workflow. We cannot.

          Short version: Please allow pull requests from other repositories/forks.

          This solves a number of issues:

          - Right now write access would be needed to the target repo [2] [3]
          - Right now there are no security limitations. "Can send a PR" means "can change our code"

          So far, PRs are 'incomplete' as far as I can tell, so [1] is really merely half the support/part of the plumbing.

          1: http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/3891599-tfservice-git-pull-requests

          2:…

          39 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 →
          • Make work item columns customizable in check-in dialog

            When checking-in our policy is that a work item has to be linked. Our work items have a custom field with an ID that differs from the TFS ID. The columns in the check-in dialog are not customizable which makes it very ennoying to find the correct work item.

            38 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

              6 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

            • Make changeset discussions more discoverable

              Provide a way to make TFS 2013 changeset discussions more discoverable. Today, there are two ways to know if a discussion is occurring on a given changeset:

              * Navigate to Web Access, then go to "Code" >> "Changeset". Look for any changesets with discussion balloon icons and click on those.

              * Create a Work Item from a given discussion so as to track it on the board and/or notify someone who has set up alerts.

              It would be preferable to subscribe to project alerts based on discussions, or to subscribe to this event in the Team Room.

              36 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 opening diffs for multiple files with a single click

                When viewing diffs in TFS, it is very time consuming to right-click on each file individually to select "compare with latest version...". Would like to be able to select multiple files, right click, compare, and have a diff window pop up for each file selected using the comparison method chosen.

                35 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

                  12 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

                • Update work items on commit for git

                  Allow resolving of work items when committing to git on Visual Studio Online.

                  34 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 →
                  • TFS Export Changesets to (.xls, .doc, .txt, .html ...)

                    If you open the menu item File->Source Control->Find In Source Control->Changesets... (you must be in Source Control Explorer for this to be available). This will open the Find Changesets dialog. You can then search for change sets by date on a given source folder but not have any button for export result in dialogs.

                    Please make additinal export button in dialog that I attach here.

                    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

                      5 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
                    • Annotate View should allow one to go back in time

                      When activating Annotate View for a source file, then one can see what revisions changed what parts of the current code.

                      It would be useful to be able to right-click a code-part-revision and choose "Show Annotate View before this revision". It would then activate a new Annotate View base on the version history from just before the specified revision.

                      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

                        5 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
                      • TFS GIT - Prevent deletion of specified branches (specified with "naming")

                        I Need to prevent users to delete our "live" branch (isn't the master). On this branch i have set branch policies etc...

                        Is there a way like "hooks" on git hub. I didn't found anything .. if nothing exist, i want so suggest!

                        Thanks

                        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

                          3 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
                        • Pull request: rest feedback of related active pull request after code changes (push new changes)

                          Branch policy: require 2 reviewers approve

                          Steps:

                          1.Pull request created with 2 reviewers
                          2.One reviewer accepted the PR and the other reviewer rejected
                          3.The author fixed and pushed up the code
                          4.The reviewer who had rejected the code approved
                          5.The PR completed successfully without the first approver seeing the update

                          It's better that the feedback can be reset automatically (can just rest approve feedback) after a push the new changes, in order to the all reviewers can review the new changes.

                          31 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 →
                          • 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.

                            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

                              0 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
                            • Allow deletion of pull requests

                              Sometimes developers issue pull requests against the wrong branch - especially when using gitflow. This is purely a mistake and the pull request should be deleted and re-issued.

                              VSO only gives the option to abandon the pull request which leaves them hanging around. They can also be re-activated after abandoning.

                              When mistakes are made, we just want them deleted.

                              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

                                4 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 →
                                  • Add support for viewing Jupyter (ipython) Notebooks

                                    I would like to be able to view formatted Jupyter Notebooks in my repositories. Notebooks are commonly and increasingly being used in the areas of Data Science and Statistical Computation and contain live code, equations, visualizations and explanatory text.

                                    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

                                      5 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
                                    • Add support for more file viewers in TFS web client

                                      In TFS web client code explorer, it is possible to view text files by clicking on them. They are then opened in a pane to the right. But it would be very beneficial to be able to view other file types as well (mainly .docx and PDF), without having to download them first.

                                      (Today, this returns the error message 'This file contains non-printable characters and no other viewer was found for file extension docx'.)

                                      We have placed a documentation repo in parallel to code repos (since we would like to store everything dev related in one place) and it would…

                                      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

                                        0 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 →
                                        • 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.

                                          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 →
                                          • Don't see your idea?

                                          Feedback and Knowledge Base