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. TFS code review should not require a new code review to be started when code that is already under review is changed based on review comment

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365428/tfs-code-review-should-not-require-a-new-code-revi.html
    It seems that TFS requires a new code review to be started whenever code that is already under review is updated in response to review comments. It is not only unnecessary busy work for a developer to initiate a new review each time a review comment would suggest a change to the code that is already under review is necessary, but it also prevents having a single picture of changes made as a result of the review process.

    With the current method, a…

    1,138 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

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

      We have a lot of investment taking place on our code review platform that will enable iterative code reviews, and we will initially bring that functionality to Git (via pull requests). Improving iterative code reviews for TFVC is still on our backlog, but it is not in our 6 month plan, so we are resetting the status.

      Matt Mitrik

    • Make visible the current working changeset at which the code is updated in TFS Source Control History

      This suggestion is migrated to Developer Community. Please use below link to view the current status.
      https://developercommunity.visualstudio.com/content/idea/365474/make-visible-the-current-working-changeset-at-whic.html
      It could be useful to see which is the current working changeset at which the source code is updated like in SVN.
      For example using a bold font for the changeset line in the History

      603 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

        1 comment  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
      • 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
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          Signed in as (Sign out)

          We’ll send you updates on this idea

          82 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

        • Allow organizing/grouping git repositories in a team project

          This suggestion is migrated to Developer Community. Please use below link to view the current status.
          https://developercommunity.visualstudio.com/content/idea/365451/allow-organizinggrouping-git-repositories-in-a-tea.html
          The ability to host multiple git repositories in a single team project was essential to get uptake of git as a source control option for larger teams.

          But with this comes organizing those repositories.

          We need a way to be able group git repositories perhaps through some sort of virtual folder structure (like adding solution folders) to help navigation when a large amount of git repositories exist in a single team project.

          426 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

            26 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
          • 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
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              Signed in as (Sign out)

              We’ll send you updates on this idea

              12 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
            • Allow the ability to prove that a code review was done for a task

              This suggestion is migrated to Developer Community. Please use below link to view the current status.
              https://developercommunity.visualstudio.com/content/idea/365449/allow-the-ability-to-prove-that-a-code-review-was.html
              I was asked to escalate this from here: http://social.msdn.microsoft.com/Forums/vstudio/en-US/5e9c476d-a728-4505-a310-9614b1c3b06f/how-to-find-a-work-items-code-review-request?forum=tfsworkitemtracking

              We are using VS2013 connected to TFS2012.

              We are currently being audited as to our development practices. Overall it is going well and we can provide evidence on our processes.

              However it seems TFS won't allow us to find a code review for a task.

              We use a 1 tier branch, so everything gets committed and released from that. Before a commit a code review request is created. Only when the code review passes…

              184 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

                14 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

              • implement branch history for folders

                This suggestion is migrated to Developer Community. Please use below link to view the current status.
                https://developercommunity.visualstudio.com/content/idea/365397/implement-branch-history-for-folders.html
                In the history of a single file the branch/rename history is visible by plus-sign on the left.
                I would like to have such a feature for complete folders which are branched/renamed.

                183 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

                  31 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
                • 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
                  Check!
                  (thinking…)
                  Reset
                  or sign in with
                  • facebook
                  • google
                    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 →
                  • Allow deletion of pull requests

                    This suggestion is migrated to Developer Community. Please use below link to view the current status.
                    https://developercommunity.visualstudio.com/content/idea/365572/allow-deletion-of-pull-requests.html
                    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.

                    150 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

                      16 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
                    • 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
                      Check!
                      (thinking…)
                      Reset
                      or sign in with
                      • facebook
                      • google
                        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 →
                      • Update work items on commit for git

                        This suggestion is migrated to Developer Community. Please use below link to view the current status.
                        https://developercommunity.visualstudio.com/content/idea/365454/update-work-items-on-commit-for-git.html
                        Allow resolving of work items when committing to git on Visual Studio Online.

                        117 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

                          15 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
                        • 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
                          Check!
                          (thinking…)
                          Reset
                          or sign in with
                          • facebook
                          • google
                            Password icon
                            Signed in as (Sign out)

                            We’ll send you updates on this idea

                            19 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!

                          • assign code review to a TFS group

                            This suggestion is migrated to Developer Community. Please use below link to view the current status.
                            https://developercommunity.visualstudio.com/content/idea/365432/assign-code-review-to-a-tfs-group.html
                            In any medium to large development environments that I know, each team has at least a few senior developers that do code review on a regular basis. We also fall in this category and we could really use a way to assign code review to a TFS Group, instead of adding each one of the code reviewers in the team to every code review request

                            103 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

                              5 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
                            • VSTS - Personal Git repositories for forking

                              This suggestion is migrated to Developer Community. Please use below link to view the current status.
                              https://developercommunity.visualstudio.com/content/idea/365505/vsts-personal-git-repositories-for-forking.html
                              Give each user a personal Git repo space. The "root" repo today is "Git Repositories". Create a special root called "My Repositories".

                              Then add a "fork" button next to the "clone" link that would automatically clone in a new repo in "My Repositories" Git folder. Repositories here should still have their origin remote and be available to submit Pull Requests against the origin.

                              Here is a manual workaround that some are following to recreate this flow:
                              http://www.woodcp.com/2014/01/how-to-fork-git-repositories-on-visual-studio-online/

                              99 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

                                7 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
                              • Add support for viewing Jupyter (ipython) Notebooks

                                This suggestion is migrated to Developer Community. Please use below link to view the current status.
                                https://developercommunity.visualstudio.com/content/idea/365561/add-support-for-viewing-jupyter-ipython-notebooks.html
                                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.

                                87 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

                                  14 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
                                • Add a checkbox in pull request file list for each file to indicate that file has been reviewed

                                  This suggestion is migrated to Developer Community. Please use below link to view the current status.
                                  https://developercommunity.visualstudio.com/content/idea/365746/add-a-checkbox-in-pull-request-file-list-for-each.html
                                  Coming from TFVC in VisualStudio to Git, one thing that makes large pull requests a little more tedious is the lack of the "done" checkbox that a TFVC code review had. Could that be added to git pull requests so that the file collapses (and remembers that you'd done it) and it's easier to come back to a large pull request over the course of a day or so, instead of having to plow through it in one sitting so you don't lose…

                                  83 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

                                    1 comment  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
                                  • Code Review after tasks in TFS completed

                                    This suggestion is migrated to Developer Community. Please use below link to view the current status.
                                    https://developercommunity.visualstudio.com/content/idea/365424/code-review-after-tasks-in-tfs-completed.html
                                    Now we can perform a code review on checked in code. But my group does incremental check ins and doesn't want a code review after checking in 4 lines of code. We would like to see code reviews after say, the developer has completed a User Story task or a user story. preferrably a task.

                                    77 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

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

                                      We have a lot of investment taking place on our code review platform, including the ability to review multiple changesets. Adding this for TFVC is still on our backlog, but it is not in our 6 month plan, so we are resetting the status.

                                      Matt Mitrik

                                    • 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
                                      Check!
                                      (thinking…)
                                      Reset
                                      or sign in with
                                      • facebook
                                      • google
                                        Password icon
                                        Signed in as (Sign out)

                                        We’ll send you updates on this idea

                                        20 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
                                      • 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
                                        Check!
                                        (thinking…)
                                        Reset
                                        or sign in with
                                        • facebook
                                        • google
                                          Password icon
                                          Signed in as (Sign out)

                                          We’ll send you updates on this idea

                                          8 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
                                        • Allow for gitflow branching model

                                          This suggestion is migrated to Developer Community. Please use below link to view the current status.
                                          https://developercommunity.visualstudio.com/content/idea/365447/allow-for-gitflow-branching-model.html
                                          We would like to allow for a git flow model. Or a simple branching model with branch permissions such that only team leads are capable of merge (after code review) and developers may only check into their feature/issue branch.

                                          http://nvie.com/posts/a-successful-git-branching-model/

                                          71 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

                                            6 comments  ·  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