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

      We’ll send you updates on this idea

      0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
    • 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
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        Signed in as (Sign out)

        We’ll send you updates on this idea

        0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
      • 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
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          Signed in as (Sign out)

          We’ll send you updates on this idea

          0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
        • 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
          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  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
          • 1 vote
            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

              0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
            • vNext Build: Update File/Product Version Without Resource Files

              We have some vb/c#/vc++ projects/solutions in our application which don't have the resource files (assemblyinfo.cs/versioninfo.cs/.rc). Currently we are using VisualBuildPro for builds and it has the ability to set the file version, production version, company name, etc attributes for the output (dll/exe) after compilation *without the resource files present in the solution*.

              We are planning to migrate to vNext build but due to lack of this feature in vNext, we are unable to go forward. Can you please provide a default build task in vNext for this.

              1 vote
              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

                0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
              • 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
                Check!
                (thinking…)
                Reset
                or sign in with
                • facebook
                • google
                  Password icon
                  Signed in as (Sign out)

                  We’ll send you updates on this idea

                  0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
                • 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
                  Check!
                  (thinking…)
                  Reset
                  or sign in with
                  • facebook
                  • google
                    Password icon
                    Signed in as (Sign out)

                    We’ll send you updates on this idea

                    0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
                  • 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
                    Check!
                    (thinking…)
                    Reset
                    or sign in with
                    • facebook
                    • google
                      Password icon
                      Signed in as (Sign out)

                      We’ll send you updates on this idea

                      0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
                    • 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
                      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  ·  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?

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

                          We’ll send you updates on this idea

                          0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
                        • 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
                          Check!
                          (thinking…)
                          Reset
                          or sign in with
                          • facebook
                          • google
                            Password icon
                            Signed in as (Sign out)

                            We’ll send you updates on this idea

                            0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
                          • 1 vote
                            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

                              0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
                            • 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
                              Check!
                              (thinking…)
                              Reset
                              or sign in with
                              • facebook
                              • google
                                Password icon
                                Signed in as (Sign out)

                                We’ll send you updates on this idea

                                0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
                              • 1 vote
                                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

                                  0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
                                • 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
                                  Check!
                                  (thinking…)
                                  Reset
                                  or sign in with
                                  • facebook
                                  • google
                                    Password icon
                                    Signed in as (Sign out)

                                    We’ll send you updates on this idea

                                    0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
                                  • 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
                                    Check!
                                    (thinking…)
                                    Reset
                                    or sign in with
                                    • facebook
                                    • google
                                      Password icon
                                      Signed in as (Sign out)

                                      We’ll send you updates on this idea

                                      0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
                                    • Make the checkstyle step configurable

                                      The checksyle step in VSO Java builds should be configuerable: By default it uses the Sun checks configuration which is too restrictive for most purposes e.g. it flags the use of the tab character. It would be better if one can define a particular checkstyle configuration. Checkstyle itself provides this through its -c command line parameter

                                      1 vote
                                      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

                                        0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
                                      • Allow inline powershell code in azure PowerShell build step

                                        When using the "Azure PowerShell" build step it is only possible to enter a Script Path for script to execute.
                                        Please make it possible to add inline scripts.

                                        1 vote
                                        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

                                          0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
                                        • Show unit test code coverage just for a particular commit

                                          The code coverage results is currently for all assemblies/all code. When I see a commit I'd like to see just the code coverage results for that change if possible. This would allow me to approve/reject based on coverage for that change.

                                          1 vote
                                          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

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

                                          Azure DevOps (formerly Visual Studio Team Services)

                                          Feedback and Knowledge Base