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. Use team fields instead of area paths to support teams

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365897/use-team-fields-instead-of-area-paths-to-support-t.html
    I found this idea has been proposed many times under different names, and everytime got archived for too few votes.
    So I will post this again if it this time would get more votes :)
    Currently one can separate Team responsibilities only by Area Path. TFS supports specific team field but VSTS does not. Plese have this functionality in VSTS too. https://docs.microsoft.com/en-us/vsts/work/customize/use-team-fields-instead-area-paths

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

    We’ll send you updates on this idea

    14 comments  ·  Work Item Tracking  ·  Flag idea as inappropriate…  ·  Admin →
  2. Improve hosted build agent performance with build caches

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365799/improve-hosted-build-agent-performance-with-build.html
    Consider options to reduce build time of hosted build agent significantly. I don't have problem paying for improved performance if there were such option.

    For example dotnet restore build task takes 95 seconds for simple asp.net core 2 app in each build. Packages could be cached.

    Agent initialization takes 39 seconds. Agent could be initialized in advance, why not?

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

    We’ll send you updates on this idea

    56 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  3. Export documentation from Wiki

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/379609/export-documentation-from-wiki.html
    it would be useful if VSTS Wiki would allow to export documents to PDF documents.

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

    We’ll send you updates on this idea

    19 comments  ·  Wiki  ·  Flag idea as inappropriate…  ·  Admin →

    Can you please raise a bug @ https://developercommunity.visualstudio.com/spaces/21/index.html regarding the issue you are facing with printing a wiki page.

    When you export a hierarchy of pages, would you like to export it to PDF or would you expect other formats as well such as HTML, .docx, etc. or that does not matter much.

    Sandeep Chadda
    follow aka.ms/devopswiki to know latest about wiki
    tweet @sandeepchads to talk to me about VSTSWiki

  4. 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
    (thinking…)
    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 →
  5. Migrate a shelveset to a different branch

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/366130/migrate-a-shelveset-to-a-different-branch.html
    Restore functionality in TFS/TFVC 2017 to migrate a shelveset to a different branch when unshelving.

    This functionality was available in Powertools 2015 via

    tfpt unshelve /migrate /source:"$/ProjectName/Branch" /target:"$/ProjectName/Targetbranch" "My Shelveset Name"

    But there is no equivalent or workaround for vs 2017 as far as I can tell.

    (https://stackoverflow.com/questions/49371144/visual-studio-2017-cannot-move-shelveset-to-another-branch)

    Moving incomplete work between branches as release dates change, or new work comes in is a common practice for us.
    Now we have to temporarily commit incomplete/broken work to merge it into other…

    20 votes
    Sign in
    (thinking…)
    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 →
  6. Add Upstream Sources for Maven feeds

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365864/add-upstream-sources-for-maven-feeds.html
    Add Upstream Sources for Maven feeds to proxy maven central or other maven repositories

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

    We’ll send you updates on this idea

    6 comments  ·  Package Management  ·  Flag idea as inappropriate…  ·  Admin →
  7. wiki notifications

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/379604/wiki-notifications.html
    We need a Wiki subscription. I would like to know (and would like me team to know) when a Wiki page as been updated or if a new Wiki page has been added. Very important to the communication and collaboration value of the Wiki

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

    We’ll send you updates on this idea

    37 comments  ·  Wiki  ·  Flag idea as inappropriate…  ·  Admin →

    I almost hear 3 feedback items here:
    1) Service hooks to integrate with other tools such as Slack, MSTeams etc.
    - This makes sense.

    2) Simple notifications on page updates
    2.1) Ability to follow a page to accomplish (2) i.e get notifications on page updates
    - This resonates with me a lot. I think we need to introduce Follow for a wiki page.

    3) Notifications when anything in the whole Wiki repo is updated. I feel this is a more admin rather than a user level feature .. am I thinking right?

  8. Add Permalinks in Wiki

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365921/add-permalinks-in-wiki.html
    Please integrate permalinks in wiki to avoid wrong links after moving single wiki pages.

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

    We’ll send you updates on this idea

    8 comments  ·  Wiki  ·  Flag idea as inappropriate…  ·  Admin →
  9. Library of Variable and Task groups shared between all projects

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365752/library-of-variable-and-task-groups-shared-between.html
    We need a library in VSTS to manage and share Variables and Tasks Groups between projects, with one definition of a Variable or a Task Group, and not import/export of a Variable or a Task Group which can become different in each project.

    Lot of projects uses common variables and task. And we need to create only on copy of a Variable or Task group to prevent their duplication with importations, and without to go out of VSTS.

    Thanks.

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

    We’ll send you updates on this idea

    27 comments  ·  Release Management  ·  Flag idea as inappropriate…  ·  Admin →
  10. Enable Build Expiration for Manually triggered build policy in PR

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/366032/enable-build-expiration-for-manually-triggered-bui.html
    When setting a Build Validation Policy for a branch, the option for Build Expiration is disabled when the Trigger is set to Manual.

    Allow Manually triggered builds to expire when new code changes are pushed to the source branch within an open Pull Request.

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

    We’ll send you updates on this idea

    3 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  11. Use dropdowns in variables of vNext build definitions

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365862/use-dropdowns-in-variables-of-vnext-build-definiti.html
    Make it possible that use dropdowns in variables of vNext build definitions in TFS.

    Original post:
    https://stackoverflow.com/questions/48279008/use-enumerations-dropdowns-in-variables-of-vnext-build-definitions-tfs

    59 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 →
  12. Provide same rich markdown/wiki editor for published code as for provisioned wikis

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/379618/provide-same-rich-markdownwiki-editor-for-publishe.html
    As documentation structure in an enterprise environment is much more complex and approval (compliance) is unavoidable, use of provisioned wiki in Azure DevOps becomes too limited.

    We would like to suggest the following features to improve the UX of "published code" wikis for all users (also non-developers):

    Enable wiki editor for "published code wiki" with same features and functionalities as in provisioned wikis.
    Enable commit and pull request flow from the editor (wiki).
    Enable all commit features (such as broken link detection) for…

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

    We’ll send you updates on this idea

    2 comments  ·  Wiki  ·  Flag idea as inappropriate…  ·  Admin →
  13. Always do autosave (drafts) on VSTS Wikis

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/366066/always-do-autosave-drafts-on-vsts-wikis.html
    I just lost two hours of work on a Wiki page (documentation) because I did not want to "commit" partial results, and VSTS apparently does not autosave the Wiki pages *at least* to some temporary location every few minutes. It does ask if you want to leave the page, but if you press ESC, this is apparently regarded as a confirmation (at least on Firefox ESR 60)!
    This is extremely frustrating. Please add an autosave option that is enabled by default, and if…

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

    We’ll send you updates on this idea

    8 comments  ·  Wiki  ·  Flag idea as inappropriate…  ·  Admin →
  14. Wiki - mermaid & plantuml support

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365751/wiki-mermaid-plantuml-support.html
    Love the wiki functionality.

    It would be great to get support built-in or via user extensions for mermaid (https://mermaidjs.github.io/) and plantuml (https://github.com/plantuml/plantuml).

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

    We’ll send you updates on this idea

    22 comments  ·  Wiki  ·  Flag idea as inappropriate…  ·  Admin →
  15. Allow Import of pipeline for project with no pipelines.

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/366320/allow-import-of-pipeline-for-project-with-no-pipel.html
    When I enter a project with existing build pipelines, I get a menu on the left that I can import a template pipeline from. When there are no build pipelines created yet, this menu does not appear and I have to create an empty build pipeline, to then be able to access the menu to import my real build pipeline.

    Could you make it possible to import a build pipeline on a project where none exist yet.

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

    We’ll send you updates on this idea

    3 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  16. Clone Variable Groups

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365724/clone-variable-groups-1.html
    Being able to clone an existing Variable Group in the VSTS Build & Release Library.

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

    We’ll send you updates on this idea

    26 comments  ·  Release Management  ·  Flag idea as inappropriate…  ·  Admin →
  17. Add "include page" like capability

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/366131/add-include-page-like-capability.html
    It is fairly common to have identical content displayed in different pages. To ease maintenance it's helpful if that content is managed in just one place but can then be displayed in many. Some Wikis support the notion of an "Include Page" to hold the reused content. That is VERY helpful, and DRY (Don't Repeat Yourself):

    https://en.wikipedia.org/wiki/Don%27t_repeat_yourself

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

    We’ll send you updates on this idea

    5 comments  ·  Wiki  ·  Flag idea as inappropriate…  ·  Admin →
  18. Allow Stakeholders to view wikis published from code

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365939/allow-stakeholders-to-view-wikis-published-from-co.html
    The new "Publish markdown files from Git to Wiki" feature (https://blogs.msdn.microsoft.com/devops/2018/03/25/announcement-publish-markdown-files-from-your-git-repository-to-vsts-wiki/) is great, but while Stakeholders can view normal Wikis, Wikis published from Git don't appear for Stakeholders.

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

    We’ll send you updates on this idea

    3 comments  ·  Wiki  ·  Flag idea as inappropriate…  ·  Admin →
  19. 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
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    85 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

  20. Delivery Plans - Features over sprint boundaries

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365685/delivery-plans-features-over-sprint-boundaries.html
    Delivery Plans Extension has the potential to show the planning for future features we implement to our stakeholders. We work in sprints of 3 weeks. Often, the development of a feature takes more than one sprint. It does not seem possible to let an epic or feature run over two sprints. Is that something you have considered? Or is there any smart work around?

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

    We’ll send you updates on this idea

    27 comments  ·  Work Item Tracking  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 264 265

Azure DevOps (formerly Visual Studio Team Services)

Feedback and Knowledge Base