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. Support "Custom Editor" template for Extensibility - VSPackage (VS 2017 Extensibility Template)

    We always use Visual Studio (Isolated) Shell project template to create special IDE for instrument control, like run instrument workflow, data transfer, automation DAQ task, etc. use VS Package and MEF to extend my isolated shell, use "Project System" to create custom project type, and always create "Custom Editor" and "Custom Designer" to implement GUI.

    So we recommend support VS 2017 Extensibility Template:
    VSPackage - Custom Editor
    VSPackage - Wizard
    VSPackage - Service
    VSPackage - OptionPage (WPF)
    VSPackage - DialogWindow (WPF)

    1 vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  2. Make it possible to add link in TFS build log (e.g. in error messages)

    It would be great, if I would be able to add link to the error message in a custom build task, where the user can find further related information. The below linking possibilities would be cool:

    - refer to a log file in the build
    - file path (server path or network share)
    - work item, changeset, shelveset
    - web url

    1 vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  3. Enhance associate work items in vNext builds

    Since the release of vNext builds we have missed full support of build association of work items. Today we can see which work items are associated with a vNext build if we open the build details or "Assign Build" in MTM.
    However, we're still facing GAP's between XAML builds and vNext builds, and I suggest the following improvements:

    1. Associate parent PBI/User Story/Requirement, preferably if all dev tasks are completed. This worked in XAML builds and is very handy for QA and PO to trace which and when PBI's are integrated and can be tested.
    2. Add a tab in…

    1 vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  4. In the powershell task in either the build or release management

    In the powershell task in either the build or release management the script argument is relatively small. For instance, i have about 15 variable that i am passing into my powershell script for configuration. But after only a few argument, you are unable to see the rest of your argument. Could you make that textbox adjustable ?

    1 vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  5. have visual studio & msbuild steps fail by error code

    have visual studio & msbuild steps fail by error code instead of text patterns like "error" or "warning"

    this would get rid of that "illegal characters" error that is so hard to fix in very large projects

    1 vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  6. Allow Work Items associated with a vNext build to be customised/filtered

    Using TFVC we create code reviews that are associated with the checkin, we sometimes also associate Tasks. These associations are needed for traceability, but they get included in the "Associated Work Items" section of a build summary, all we really want are the Bugs and Change Requests.

    It would be good to be able to customise something (the build definition?) to say what Work Item Types should be included in the Associated Work Items list.

    1 vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  7. Rework Artifacts, look at TeamCIty

    Seriously. In TeamCity the artifact generation works like this:

    A text bos, one entry per line

    SourcePath => TargetPath

    Multiple matches possible.

    **/*.bin => binaries
    **/*.exe => binaries
    -> both to binaries folder

    **/*.exe => binaries.zip
    Guess what, zip file.

    Right now I would need 3 entries for that. This is not efficient for more complex configurations..

    Same with extractions for another step.

    binaries.zip!blabla.exe => binaries
    -> takes blabla.exe out of binaries.zip to move it to a binaries folder.

    Textbox again, multiple lines possible.

    Team Services handling is like generations behind, sadly.

    1 vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  8. Shelveset builds should have a "Build Reason" of Private (vNext Builds)

    Shelveset builds for xaml build definitions had a build reason of Private. This meant you could easily filter them out in a build alert (I don't want the whole team notified about a build I'm running to test my changes). However in vNext Builds they have a Build Reason of "Manual", which makes them impossible to distinguish from our manual release builds.

    1 vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  9. 1 vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  10. Enable moving multiple Build Defs into a Build Def folder

    Currently you have to select build defs one at a time to move into managed build def folders. Would like the ability to select multiple build defs to move to a given folder.

    1 vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  11. Release buildserver image as an ARM template in Azure

    Release the buildserver image as an template in Azure to create hosted build controllers for VSO or TFS on-premises

    1 vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  12. Work items associated to build is limited to 50 work items

    Can this figure be increased or at least adjustable? Where we are creating a build after a large merge from another branch, we're missing work items associated with the build as only 50 get associated. I've adjusted our merge script to try to filter out tasks and code reviews that also get associated

    1 vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  13. Option to choose a build agent from build services and setup a agent in Azure

    Currently we have to setup a VM or a machine for build and then configure an agent on it. Its good to have both together as a feature in VSTS provide this service as PaaS. User should not have to setup a VM he should only be choosing like release deploy. However we should retain existing build machine on-premise VM setup also.

    1 vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →

    Hi, I’m trying to see if this should be grouped with any other posts and am not sure I’m fully understanding the request.

    We do provide Hosted Build and Release pools where you can use VM’s that we manage. We also have Azure Agent extensions that will set up the VSTS Agent for you if you’d rather manage your own cloud infastructure

    … or do you mean something else altogether?

  14. Add the ability to exclude "draft" builds from reporting to Slack/Service Integrations

    Currently we set the service hook to report for all build definitions and noticed that even draft definitions were getting reported to the slack channel. As we have a lot of builds per team project setting them explicitly is not really feasible. It would be nice if they were filtered by default or if there was an option not to report draft builds.

    1 vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  15. Install TypeScript Tools 2.1.4 on Hosted Build Servers

    Hosted build agents currently only support TypeScript 2.0

    TypeScript 2.1.4 has been out for a while now but is not available on the hosted agents (https://www.microsoft.com/en-us/download/details.aspx?id=48593). In general it would be nice if the build agents were updated with the latest typescript versions in a more timely fashion. E.g. a week or two after they are released.

    1 vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  16. 1 vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  17. Is that Possible to see a Button or some property is that we can hide all commented green lines before printing a document.

    Is it possible to have a function or button that hides all green commented lines before we have a print.

    Comment lines are useful, but sometimes we need to see the clean code on the press.

    So this tiny method can be easy for us before printing our codes.

    1 vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  18. 1 vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  19. Allow build scheduling for vNext through parameters in a json post request

    Currently you can use a json object or data to queue a build for vNext. However there are no parameters available that will allow you to schedule it for a specific time.
    Based on my tests/trials the only thing missing is the start time parameter. You can already pass in the parameter that shows the schedule icon...
    It would be nice to have this functionality. I know you can set a schedule in the build definition GUI but that is not what I want to do since this will be from an external app that my team mates use.

    1 vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  20. Allow Test/Production Driver Signing

    The current driver signing features of a project do not work with TFS Build. Both the XAML and vNext build systems output a "SIGNTASK (0, 0)
    The signer's certificate is not valid for signing." error when attempting to build.

    I opened a case with Microsoft (116012013608802) and it has been concluded that it is a limitation of the build system unless it is run as an interactive process. Not sure what the point of a build server is if things need to be ran as an interactive process with a user logged in all the time.

    On-Premise build servers should…

    1 vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →

Azure DevOps (formerly Visual Studio Team Services)

Feedback and Knowledge Base