Azure DevOps (formerly Visual Studio Team Services)

Announcement: Last fall, we migrated this forum to Developer Community to provide you one convenient and responsive system for all feedback. As the final step in the migration, this forum will be closed off completely on June 1st, 2019. We encourage you to visit Azure DevOps Developer Community where you can now suggest new ideas, browse and vote on existing ideas, and engage with Azure DevOps teams

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. 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
    (thinking…)
    Sign in with: facebook google
    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

  2. Comments in a commit should show up in the Pull Request

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365529/comments-in-a-commit-should-show-up-in-the-pull-re.html
    If I go to a Pull Request, click through to a commit and add comments to files there, none of the comments peculate up to the Pull Request.

    40 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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.

    38 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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
    (thinking…)
    Sign in with: facebook google
    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

  5. Pull request: rest feedback of related active pull request after code changes (push new changes)

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365629/pull-request-rest-feedback-of-related-active-pull.html
    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.

    37 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
  6. Web Based Code Review

    We are a mixed development environment, using both TFVC and TF-GIT for code control. Many of our developers are linux based and do not use visual studio. We can do everything we want through the web interface, with the one major exception of code reviews. These only function fully through visual studio. I would like to see full code review functionality via the online portal.

    37 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    8 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
  7. New Navigation: Team pull requests

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/366018/new-navigation-team-pull-requests.html
    In the new navigation it would be great to see the pull requests that are assigned to a team that I'm a member of, in addition to those I created. Like in the old/current 'My Pull Requests' page.

    35 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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/.

    35 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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
    (thinking…)
    Sign in with: facebook google
    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

  10. Ability to see labels in browser view / TFS Web Access

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365544/ability-to-see-labels-in-browser-view-tfs-web-acce.html
    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 :)

    34 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
  11. TFS New Service Endpoint with ssh key for External Git

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365623/tfs-new-service-endpoint-with-ssh-key-for-external.html
    For now the new service endpoint dialog only has fields for url, username/password one option.

    I need to be able to also supply a ssh key for authentication. Please add this feature.

    32 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
  13. Git Statistics Reports

    It would be great if we could see reports on git activity similiar to what you can view on github for git repositories on VSO.

    30 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
  14. Add Preview for AsciiDoc (.adoc) files in addition to Markdown

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365715/add-preview-for-asciidoc-adoc-files-in-addition-to.html
    Allow README.adoc files to be previewed in VSO > Code > Files the same as README.md.

    GitHub supports AsciiDoc format via Asciidoctor.

    29 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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.

    29 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
  16. Have branch police template to store the branch policies usually set for most branches

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

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

    28 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
  17. Filter pull request comments

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365643/filter-pull-request-comments.html
    Would be nice to have a "filter comments" in the pull requests so we could filter our Resolved and Closed and focus and what's still outstanding in the review.

    28 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
  18. Disable comment editing (i.e. add, edit, delete, and state change) in completed pull request

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365593/disable-comment-editing-ie-add-edit-delete-and-sta.html
    After completing a pull request, I noticed that team members can still add comments and the comment authors can still edit and delete their own comments. It would be ideal for these controls to be locked down after a pull request is completed. This way we can use the completed pull request as audit trial.

    Also, the original comments' states (i.e. active, pending, resolved, won't fix, and closed) can still be changed too, making them susceptible to either intentional or unintentional modifications. For…

    28 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
  19. Add the ability to mark files as reviewed

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365577/add-the-ability-to-mark-files-as-reviewed.html
    When doing code reviews for large pull requests, I often get pulled away to do something else and then come back later to continue reviewing. It would be very helpful to be able to mark which files I've reviewed as I review them so that I can more easily pick up where I left off, and not re-review the same files multiple times.

    28 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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?

    28 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

Azure DevOps (formerly Visual Studio Team Services)

Feedback and Knowledge Base