Visual Studio Team Services

We’d like your suggestions and ideas to help us continuously improve future releases of Visual Studio Team Services (VSTS) 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 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. Widen or Allow Resize PR Comment | Better 4K Support

    Please see the screenshot. I shouldn't have to scroll... I have plenty of real estate that VSTS is not using! 😜

    1 vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)

      We’ll send you updates on this idea

      0 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
    • Add colour blind mode / dark theme for reviewing Git pull requests

      I am colour blind. When reviewing pull requests, I have great difficulty in seeing code edits quickly, as these are highlighted by pale green lines, which are not easy to spot on a light background, and are themselves highlighted with a slightly darker green shading on the actual edit. These two highlights are so close together in terms of their colour that I find them virtually impossible to tell apart, meaning that I cannot tell at a glance precisely where the edit is. VSTS is really not colour blind friendly in this regard. A colour blind mode is needed, or…

      1 vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        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 me to see what items (files/folders) are present on my mapped local path

        Visual Studio allows me to see all files in the solution explorer with the click of a button. this allows me to see exactly what is in the related solution folders shown with ghosted-like icons. Allow this same concept in the TFS Source Control Explorer tab. this would make it far easier to see what the locally mapped path contains and what the server contains. I get that it is easy to add a file to the source control when working with solutions but source control is not a solution centric concept. most of my projects are not visual studio!

        1 vote
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          Signed in as (Sign out)

          We’ll send you updates on this idea

          0 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
        • Creating Pull Request suggests always to merge to master

          When I create a PR in VSTS, the current behaviour is that PR suggests merging always to "master" branch. In cases when I have originally branched from somewhere else than "master" (e.g. ReleaseXYZ), this is annoying since I might not want to merge my changes to master but back to the original branch I did my feature/work branch from.

          Could it be configurable that in project or per user creating a new PR would suggests to merge to branch where PR branch has been branched from or to master branch ?

          1 vote
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            Signed in as (Sign out)

            We’ll send you updates on this idea

            0 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
          • Pull Request should show diff between head of source branch and head of target branch (instead of common ancestor)

            Currently, as noted in the link below, the Git Pull Request diff that is shown is the diff between the head of the source branch and the common ancestor of the source and target branch. This does not reflect the result of the merge (and also doesn't match any build validation that is run).

            It would be much more useful to see a preview of the final product, thanks!

            https://developercommunity.visualstudio.com/content/problem/107670/vsts-pull-request-changes-list-completely-differen.html

            2 votes
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              Signed in as (Sign out)

              We’ll send you updates on this idea

              0 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
            • versioned item missing tfs 2017 update 3

              versioned item missing tfs 2017 update 3

              TFS 2017 Update 1 to Update 3 - After upgrading from TFS 2017 update 1 to update 3, we are now missing "Versioned Item" under links section.

              "Versioned Item" previously existed in links in TFS 2017 Update 1 and we have many users looking for them.

              Trying to determine if this is a bug or if we are missing a new location and/or representation of "Versioned Items" in links.

              Thanks in advance for assistance and guidance.
              Brian C.

              1 vote
              Sign in
              Check!
              (thinking…)
              Reset
              or sign in with
              • facebook
              • google
                Password icon
                Signed in as (Sign out)

                We’ll send you updates on this idea

                0 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
              • show absolute time of commits in commit history view

                In the commit history on VSO, the commit timestamp for recent commits is relative (e.g., "16 hours ago"). This makes it difficult to compare the timestamps of two commits; for example, when figuring out if a commit made it into a particular build. Please show absolute times, or at least make it configurable.

                1 vote
                Sign in
                Check!
                (thinking…)
                Reset
                or sign in with
                • facebook
                • google
                  Password icon
                  Signed in as (Sign out)

                  We’ll send you updates on this idea

                  0 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
                • Display pull request policy status in pull request list

                  It would be helpful if there was some indicator on the pull request list whether each pull request has satisfied the policy constraints and is ready for final review/completion/whatever. Currently there is no way to quickly see which pull requests have satisfied all policies.

                  1 vote
                  Sign in
                  Check!
                  (thinking…)
                  Reset
                  or sign in with
                  • facebook
                  • google
                    Password icon
                    Signed in as (Sign out)

                    We’ll send you updates on this idea

                    0 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
                  • link to the reviewer team

                    In pull request page, reviewers list, if an item is a team, please provide a link to this team's members page, so I can easily know which people are in this team and push them to start a review.

                    1 vote
                    Sign in
                    Check!
                    (thinking…)
                    Reset
                    or sign in with
                    • facebook
                    • google
                      Password icon
                      Signed in as (Sign out)

                      We’ll send you updates on this idea

                      0 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
                    • PR push notification email should include the diff between the iterations

                      When a new iteration is published on an existing PR, it would be great to include the diff between the two iterations into the body of the email being sent (unless of course the diff is huge). This is also related to auto-resetting votes on the PR. An approver needs to be able to tell quickly whether the change should be re-reviewed, or perhaps that the updates were benign.

                      2 votes
                      Sign in
                      Check!
                      (thinking…)
                      Reset
                      or sign in with
                      • facebook
                      • google
                        Password icon
                        Signed in as (Sign out)

                        We’ll send you updates on this idea

                        0 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
                      • Display Webhook Response Body in history

                        We are playing around with webhooks for deploying to Azure. it works great- our azure function is returning some results in addition to status 200 on response as a json document (application/json) it would be nice if that json document were visible when looking at the webhook history we can see the full request and event.. so why not the full response- Specifically, it would be nice that when choosing the Response view to see what came back from the webhook call. As an example- currently what we see under the response view is :

                        Status Code: 200
                        Reason Phrase:…

                        1 vote
                        Sign in
                        Check!
                        (thinking…)
                        Reset
                        or sign in with
                        • facebook
                        • google
                          Password icon
                          Signed in as (Sign out)

                          We’ll send you updates on this idea

                          0 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
                        • New files in Visual Studio Team Services should highlight entire file as green

                          New files that are added to a pull request in the online VSTS viewer show the contents with a white background. This is confusing in reviews because it looks like a file with no changes added to the review instead of a completely new file.

                          In the desktop Visual Studio diff viewer and in other tools like GitHub online diff viewer the background for lines in new files are highlighted green to indicate they are additions to the code base.

                          1 vote
                          Sign in
                          Check!
                          (thinking…)
                          Reset
                          or sign in with
                          • facebook
                          • google
                            Password icon
                            Signed in as (Sign out)

                            We’ll send you updates on this idea

                            0 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
                          • Complimentary Pull Request Comment Status

                            Regarding this tweet, https://twitter.com/ScottJBatson/status/975073073371238400, a new, complimentary comment status could improve the pull request experience for developers in our company. The current five statuses of Active, Pending, Resolved, Won't fix and Closed either "feel negative" or hide the comment in the UI.

                            Alternatively, allowing customization of these statuses could solve this want.

                            1 vote
                            Sign in
                            Check!
                            (thinking…)
                            Reset
                            or sign in with
                            • facebook
                            • google
                              Password icon
                              Signed in as (Sign out)

                              We’ll send you updates on this idea

                              0 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
                            • Add option, and report, to skop large >50Mb files during import to git repo from TFVC

                              Rather than removing them the source folders before the import, which is problematic with validated systems, it would be great if the import from TVSC into a new git repo had an option to skip files that are too large (says > 50Mb on error). And at the end of the import, display a list of the file paths to those that are skipped.

                              1 vote
                              Sign in
                              Check!
                              (thinking…)
                              Reset
                              or sign in with
                              • facebook
                              • google
                                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 →
                              • Add Blame / Annotate feature for Pull Requests

                                When reviewing a Pull Request, I should be able to see who changed the code last.

                                0 votes
                                Sign in
                                Check!
                                (thinking…)
                                Reset
                                or sign in with
                                • facebook
                                • google
                                  Password icon
                                  Signed in as (Sign out)

                                  We’ll send you updates on this idea

                                  0 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
                                • Default source branch in "New branch..." dialog should be branch linked to parent work item

                                  When selecting "New branch..." from a work item in the sprint backlog, by default it currently will always show the master branch as source branch. By default it should show a branch linked to a parent work item if a link exists.

                                  1 vote
                                  Sign in
                                  Check!
                                  (thinking…)
                                  Reset
                                  or sign in with
                                  • facebook
                                  • google
                                    Password icon
                                    Signed in as (Sign out)

                                    We’ll send you updates on this idea

                                    0 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
                                  • Implement "Go To Definition (F12)" as a right-click menu option in VSTS pull requests

                                    In TFS code reviews, we had the option of using F12 to go to the definition of methods defined within the file being reviewed. This worked both for new and existing code. This is a huge time saver when you have to review code that calls a new method many times. Using search takes a lot longer to find the actual method implementation.

                                    15 votes
                                    Sign in
                                    Check!
                                    (thinking…)
                                    Reset
                                    or sign in with
                                    • facebook
                                    • google
                                      Password icon
                                      Signed in as (Sign out)

                                      We’ll send you updates on this idea

                                      0 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
                                    • Support linking to a specific line of code at specific revision in a VSO repository

                                      It is nice to have an ability to share a link to a specific line of code. (As it was suggested here: https://visualstudio.uservoice.com/forums/330519-visual-studio-team-services/suggestions/7197749-support-linking-to-a-specific-line-of-code-in-a-vs ).

                                      However, the link I copy (when viewing head) is not a permalink - it's a link to head revision. So, there's a significant risk that it would no longer be meaningful as soon as someone would commit something.

                                      Copying a link to a specific revision requires few more clicks, which is annoying. There should be a faster way to do that. You should suggest both options "copy permalink to this revision" and "copy link to this…

                                      1 vote
                                      Sign in
                                      Check!
                                      (thinking…)
                                      Reset
                                      or sign in with
                                      • facebook
                                      • google
                                        Password icon
                                        Signed in as (Sign out)

                                        We’ll send you updates on this idea

                                        0 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
                                      • Should be able to COPY the branch name from the branch page.

                                        There's the name of the branch on the PR page and on the branch history page, but it fights you when you try to copy the text.

                                        Any web page that has text that cannot be copied is an abomination, and some mixture of laziness and bad design. If I can't copy the text it infuriates me. Simple things, big differences.

                                        1 vote
                                        Sign in
                                        Check!
                                        (thinking…)
                                        Reset
                                        or sign in with
                                        • facebook
                                        • google
                                          Password icon
                                          Signed in as (Sign out)

                                          We’ll send you updates on this idea

                                          0 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
                                        • Make it easier to view people's PRs than it is to COMPLETE THEM!

                                          Folks shouldn't be able to complete other peoples PRs. Period.

                                          Allowing this is a strange etiquette problem, perhaps it should key into the org chart (my lead should be able to submit my PRs, but not my peers...). At very least, this option shouldn't be a gigantic blue button that's next to the very small dropdown button that includes the CodeFlow link. Literally everyone opens this page and uses it to find CodeFlow, and it's really easy to miss the 'view' link and accidentally SUBMIT someone else's change.

                                          Is it possible anyone thinks this is good? This is a really…

                                          1 vote
                                          Sign in
                                          Check!
                                          (thinking…)
                                          Reset
                                          or sign in with
                                          • facebook
                                          • google
                                            Password icon
                                            Signed in as (Sign out)

                                            We’ll send you updates on this idea

                                            0 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
                                          ← Previous 1 3 4 5 39 40
                                          • Don't see your idea?

                                          Feedback and Knowledge Base