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. Automatically associate merged changesets to their original work item so that they can be tracked with "Track Work Items"

    Here is the scenario: I code a feature in a feature branch and associate the work item. Later down the rode that feature gets integrated into the main branch prepping for release. If the developer forgets to associate the merge to the original work item, you can't use the "Track Work Item" feature to visualize where that work item ended up in the code base.

    I'd like to see something maybe like this:
    http://geekswithblogs.net/jakob/archive/2011/05/17/automatically-merging-work-items-in-tfs-2010.aspx
    http://mergeworkitems.codeplex.com/

    16 votes
    Sign in
    (thinking…)
    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 →
  2. 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
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

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

    25 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
  4. store and download check-in policies

    check-in policies should be stored and downloaded from the TFS server.
    currently, custom policies must be installed on EVERY developer machine, or suffer the wrath of error messages. If stored on the server, VS could auto-update (a la clickonce) during checkin.

    11 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
  5. 45 votes
    Sign in
    (thinking…)
    Password icon
    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

  6. 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…)
    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 →

    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

  7. Provide a way to reuse files or folders in TFS source control

    Most SCC tools provide a way to reuse files or folders in source control.
    Solutions such as SVN externals, ClearCase components, Synergy sub-projects etc.
    TFS does not provide such a solution and the only way to manage code reuse is by creating complex branching schemes (which call for even more complex an error prone merging) or complex workspace mappings.

    18 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
  8. Unshelve across branches

    Commonly write some code in one branch and then have to defer the feature/fix to another release. Need to be able to shelve the changes and retreive them to the other branch. This needs to be supported in the UI.

    68 votes
    Sign in
    (thinking…)
    Password icon
    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

  9. 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
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →
1 2 41 42 43 45 Next →

Azure DevOps (formerly Visual Studio Team Services)

Feedback and Knowledge Base