Status on Visual Studio feature suggestions

Mads Kristensen

Visual Studio receives over 500 feature suggestions from customers every month on the Developer Community website. Handling that amount is a huge effort and we’d like to share with you how we handle this volume and the steps that we take to respond to them all. What happens to suggestion tickets after they’re opened, how many make it into Visual Studio, and what happens to the rest? Let’s find out.

Let’s start with the breakdown of incoming suggestion tickets in the past 6 months and what state they are in today. We find that around 15% of the suggestions are challenging to act on, and they typically fall into the following buckets.

11% – Closed as duplicate 3% – Closed due to missing info from customer 1% – Closed because they were not suggestions for Visual Studio

We do our best to follow up with customers to get more information where we can and move them into the next stage. For example, when making a suggestion to add a command to a context menu, it is important for us to know which context menu you meant.

That leave us with 85% left which are currently moving their way through the system. Here is the status of those tickets currently in our system:

40% – Closed for a number of reasons (more info below) 20% – New, not yet processed or triaged 28% – Under review and gathering votes and comments 3% – Awaiting more info from customer 3% – On roadmap (under development) 6% – Completed and released

Now let’s dig in and see what’s behind those numbers.

From New to Under Review

We have a filtering system that automatically routes incoming suggestions to the appropriate team within the Visual Studio organization. Within my team, we have established a weekly process to triage these routed suggestions and review status. The process we follow looks like this:

  1. Does this bug belong to my team?
    • If not, move it to the right team
  2. Is the suggestion a duplicate of an existing suggestion?
    • If so, close it and transfers all votes to the original ticket (happens automatically)
  3. Does the suggestion contain all needed information?
    • If not, ask customer for more information
  4. Was this suggestion already completed or in active development?
    • If so, close it as either Completed or On Roadmap
  5. If it made it this far, mark it Under Review to gather votes and comments for 90 days

By following these steps, most suggestions end up Under Review as we gather more data, refine any repos or requirements. These make up over a quarter of all suggestions.

Every time someone adds a new comment to an existing ticket, we receive an email, so we know what’s going on with each ticket along the way, and can respond if needed.

Moving on from Under Review

Within 90 days, we attempt to address items that are still marked Under Review. Our options are:

  1. Mark it as Completed because we implemented the suggestion
  2. Mark it as On Roadmap because it’s in active development or will be very soon
  3. Close it because it didn’t get any votes and/or we’re not able to prioritize it

When we implement a suggestion, we mark it Completed or On Roadmap. Currently, approximately ~10% of the incoming suggestions go on to be implemented or added to the roadmap.

But what about the ones that don’t?

Reasons for closing suggestions

Most suggestions are good suggestions and it’s always painful to close them. Especially because a lot of them are some that we personally would like to see implemented. As developers, you know that time and resources are finite, which means we can’t implement all suggestions.

The reason we close suggestions is a mix of multiple factors, such as:

  1. It didn’t receive any votes after 90 days as Under Review
  2. It got a few votes, but an implementation will not fit within our available resources
  3. It involves areas in Visual Studio that see little usage by our customers
  4. It has negative side-effects such as degraded performance, accessibility etc.

Over a third of all suggestions end up closed due to one or more of the above reasons.

On the positive side, even for some suggestions that we close, we do move the capability into an experimental extension for Visual Studio. This allows us to lower the cost of delivering a quality product investment, and where we can draw more interest from the community.

Suggestion completed

6% of all actionable suggestion tickets end up marked as Completed. It may not sound like much, but it is about 1 suggestion per weekday. Let that sink in. Every single weekday, the Visual Studio engineering team implements a community submitted suggestion.

Before we implement a suggestion, we first write a spec for it if needed. Then we schedule the work item in a sprint for engineering to pick up. The implementation sometimes require work by multiple teams to coordinate, so they can each do their piece of the feature.

After automated test and compliance runs have finished, it’s time for code review before the code starts its journey toward the Visual Studio master branch. More automated testing runs and finally manually testing follows. After fixing all identified bugs, the completed suggestion makes its way to a Visual Studio Preview release for user testing and stabilization.

So, how do we decide to implement suggestions and how can you optimize the chances of your suggestion making it? We look at several things:

  1. Suggestions with many votes and continuous votes over time
  2. Suggestions in areas that see lots of usage by our customers
  3. Suggestions that are easier to implement
  4. Suggestions that would improve Visual Studio’s competitive advantage
  5. Well written suggestion with all relevant information in the description

A different way to think about it is to turn it around. Imagine someone wanted you to implement a feature in your product. It’s in the best interest of our product and customers to complete as many suggestions as possible, and we strive to do so.

The best times are when we get to make a lot of people happy with a feature implementation based on a suggestion.

We can must do better

We’ve gotten feedback that this process feels like a black box. Customers feel like they don’t get a response and they don’t know the status of their suggestions.

After submitting a suggestion, there is no transparency into the process, and it ends up closed without any good reason 6 months later. I end up feeling frustrated and angry. I don’t want to submit another suggestion just to be ignored. – Anonymous Visual Studio user

This is not acceptable. We must do better.

Some ideas that we are working on within the team are as follows. And, we welcome your feedback on what we might do more of to help you understand the process better.

First up, we want to be much more transparent about the process. That’s exactly what this blog post aims to achieve.

Secondly, we must be faster at responding to new suggestions. That means triaging them within the first week, so we can bring down the 20% of new untriaged suggestions to a minimum. It also means not leaving any suggestions to linger for months. This will add visibility into what is going on with the suggestions much earlier and throughout its various phases. We’ve made great progress with this in the past 6 months, but still have a bunch of open tickets to go.

Thirdly, we need to be better at giving reasons for closing tickets. Individually written by the program manager that closed them and not an automated response. As we’re getting better at handling the vast amount of incoming suggestions, this is where we’ll focus next.


I hope this blog post helps shed light on the way we handle suggestion and how we plan to improve. Completing a suggestion every single weekday will hopefully encourage you to continue opening suggestion tickets.

In closing, we’d really like to hear your thoughts or questions. What could we do better and what do we do well? Let us know in the comments below.


Discussion is closed. Login to edit/delete existing comments.

  • MgSam 0

    I think you’re missing a big reason the current process is suboptimal. The feature suggestion system sucks!
    o The search function is terrible.
    o Tickets do not have public ids, so sharing existing tickets, and having the community assist in duplicate identifcation, is impossible.
    o The controls for writing up features uses a 3rd-rate rich text control which doesn’t support Markdown (why does Microsoft refuse to use Markdown controls? You guys have owned Github for nearly 2 years, just take the controls from there.)
    o There’s no way to subscribe to existing tickets.
    o Even getting to the feature suggestion hub is confusing mess. Navigate to Wait for the page to slowly load all its content. They’ll be 3 quick links on the bottom which are only for bug reporting (Setup, IDE, All). Click any of them. Now you’re on Click the Features tab. Literally the only way to view the existing feature suggestions. No wonder its so hard for them to get votes!
    In short, you need to move feature suggestions to a Github project. 
    And this isn’t related to VS- but the formatting of this post will likely be destroyed. Because the MS blog system is less functional than something from 1996. 

    • SeanMicrosoft employee 0


      Thanks for taking the time to let us know what needs improvement on Developer Community site. Markdown, hub page experience and community assist in duplication are among the areas we are either already working on or planning to improve in the near future. Regarding subscribing, you can subscribe to a suggestion using the follow button on the suggestion details/discussion page to the right of the suggestion title. Voting or commenting on a suggestion also sends you notifications on any updates to the suggestion. Please let me know if that helps. Thanks for all your input. We recognize search needs improvement. I’d like to connect with you and understand in more detail what specifically about search that didn’t work for you. If interested, please ping me at seiyer at so we can talk briefly and learn from your experience. 



      Visual Studio Feedback Team

    • Steve Valliere 0

      I agree with MgSam’s comments and would like to clarify/expand my ideas about a couple:
      * Search:  I have trouble coming up with the same words/terms that others use in their suggestions, making searches difficult.  When the search engine attempts to “help” by trying to match variations of spelling, tense, sometimes even semantics it usually (but not always) finds things even less related that I would find without such help.  And at times, I want (actually *NEED*) the search to be EXACT matches only, preferably including quoted phrases, because I am looking for something specific that I have already seen.  The current search makes that almost impossible by matching everything under the sun that includes similar words.
      * Duplicates:  The article mentions that duplication notices are (with should/will) being written by humans.  However, those humans really need to explain (A) Just WHY/HOW the current item duplicates another and (B) leave the duplicate open for at least a couple days to give the original poster an opportunity to dispute the duplication.
      For example, I recently had an item closed as a duplicate, so I asked, in the “original” comment stream, how my item was a duplicate and explained why I thought it was not.  I received a reply on MY original (closed duplicate) thread that, after reading my post, it was decided my post was NOT a duplicate and I was asked to test a few things and reply — but the thread remained CLOSED as a DUPLICATE.  So, no my original post was misunderstood and the “correction” left it closed while asking for an impossible reply.  This is definitely an area that could use improvement.
      * Message Entry Controls:  It is frustrating for the feedback tool and the feedback web pages to use different controls and syntax.  I have found it impossible to paste even plain text into the web message edit control (for a comment) because while editing the comment, it seems to treat the pasted text as a SINGLE WORD.  A consistent system across all forms of input collection that handles cut’n’paste operations like just about everything else that exists would be a very good start.  The GIT markdown controls are a very good example of something that could do this.

  • Chuck Ryan 0

    @Mads Kristensen I am sorry but we have heard all this before, or some variation of it, and we simply do not beleive it. Sure that might be your process and it might sometimes actually be followed but in the end we are right back here with someone like you writing a blog post explaining how things are going to get better. This simple fact is that since the whole Visual Studio 2012 debacle, combined with the accellerated release schedule, Visual Studio has been on a downward spiral and is often described as buggy, bloated and slow. Each new release brings more incomplete features, many poorly designed and with plentiful bugs, which further bloats and slows down the product even more… It does not make for an enjoyable day in the office.

    • Mads KristensenMicrosoft employee 0

      I’m sorry you feel that way. I sympathise with the perspective of this being yet another promise of things improving. That being said, we’ve already made huge strides in improving our handling of suggestions and implement one suggestion every single day now. That doesn’t mean we can’t get better, but we are actaully starting to do pretty well. I hope the blog post left you with those messages too.

      • Craig Wagner 0

        While I agree that the 2017 release was buggy, the accelerated release schedule (at least of “dot” releases) meant we got fixes more quickly. 2019 has been much more stable from day 1. As applications get more complex and are comprised of dozens of solutions things are going to be a little slower, so I’m okay with that.There are two areas where I feel VS does need work:1. Building a solution the first time. There’s something wrong with the dependency tracking, and when you’re running eight concurrent compiles it often gets them in the wrong order, requiring multiple passes to get the whole solution to build the first time.2. The NuGet package manager (the visual bit, not the console). It is agonizingly slow searching for upgrades, consolidations, and installed packages. There’s got to be a way to improve that.All in all, Visual Studio is still the best integrated development environment I’ve used and I appreciate the work the team puts in. My software isn’t 100% bug free, I don’t expect anyone else’s to be either.

      • Alan DeVries 0

        We feel this way because we are tired of being ignored. Go look at the developer community at thread after thread begging you to restore the New Project Dialog to its tree-view form. They have all been either ignored or closed with not one single positive action being taken by the Visual Studio team. We aren’t asking for minor tweaks to search; WE WANT THE TREE VIEW BACK!

    • David Williams 0

      I am glad to be able to say that the negativity being voiced in some of these comments does not reflect the views and experience of the entire community. We are all developers and we all know how difficult it is to produce a complex suite of software that does everything everyone wants and has zero bugs. Visual Studio has for me steadily improved since 2012 bringing features which have significantly improved my daily working life. No everything is not perfect, but a little tolerance and patience goes a long way. I regularly post feedback when I meet a pain point from using ANY Microsoft product and so far I have not been dissapointed by the attitude taken to supporting us. I for one would like to thank MS for a lot of the hard work and effort that is put in to make developers lives easier.

      • Ondřej Linhart 0

        How hard is to not touch anything that works and not removing existing features?

      • Matthew Polder 0

        I second the views of David. I have used Visual Studio since around 1995. For years Microsoft was an opaque monolith with no way to provide feedback or suggestions. With the advent of Satya Nadella and/or their declining market share things changed. Even having a way to report feedback or a suggestion directly in Visual Studio still feels revolutionary. Could the process for responding to this be improved? Certainly. But in context, things are much better.

  • Jack Bond 0

    You failed to mention another reason Microsoft closes a suggestion…
    Microsoft is strapped for cash.
    Yep, that’s the only logical explanation for closing this suggestion. 
    And now that it’s closed, it probably can’t be upvoted. BTW, stating, it’s a “very valid suggestion” simply throws salt in the wound. Bottom line, if you’re receiving very valid suggestions, and you don’t have time to work on them in the immediate future, HIRE MORE PEOPLE. Or is it like I said, strapped for cash?
    Finally, what is it about Microsoft programmers that EVERYWHERE you have a textbox for providing input, that’s easily going to run multiple lines, the genius responsible sets the height of the textbox to 8 pixels and not resizeable?

  • Kevin Woronuk 0

    One thing that I would find helpful is the ability to find an item that has the “On Roadmap” tag on the actual roadmap.  For example, this is a feature that has the “On Roadmap” tag, but I can’t find it on the roadmap and I’d really like to know where it is.  The roadmap has linkable items to the item on the developer community page, but the reverse does not appear to be true.

    • Mads KristensenMicrosoft employee 0

      That’s a great idea!! Thanks

  • Derek Foulk 0

    “Close it because it didn’t get any votes and/or we’re not able to prioritize it”
    This is one my biggest issues with the way our reports are handled. It feels like too many good reports go unaddressed because they don’t get enough votes. Especially when we’re talking about stuff that only a minority of users are going notice. I’m guessing a small fraction of users are going to take the time to provide feedback. Even less are going to vote on issues that they didn’t try to report themselves. Heck, I forget to vote on issues I go to report, but somebody else has already done so.
    “Most suggestions are good suggestions and it’s always painful to close them. Especially because a lot of them are some that we personally would like to see implemented. As developers, you know that time and resources are finite, which means we can’t implement all suggestions.”
    I don’t believe anybody expects all reports to be acted on- just more of them. This is a Microsoft product that we pay good money for. Too many good reports are closed.
    If it’s a good suggestion, idea, but report- backlog that puppy! Groom that backlog, of course, but get it in!

    • David Lowndes 0

      Yep, voting is the aspect that gets my back up too. Suggestions/bug reports should be investigated on their own merits, not subject to a popularity contest.

      • Mike Diack 0

        Agreed too.

      • Petr Kraus 0

        I have seen this process elsewhere too. And yea, I do not understand this either. Since when time prioritization is a reason for closing a ticket. I think people incorectly use ticket system as a sprint backlog. But IMO ticket should stay open as long as it is relevant\correct. Prioritization should not even enter the discussion (unless the chosen alternative path makes the ticket irrelevant). It is weird if the dev himself agrees the suggestion should be implemented at some point, but closes the ticket anyway.

    • Ondřej Linhart 0

      Agreed 100%

  • Derek Foulk 0

    “Your suggestion has been queued up for prioritization. Feature suggestions are prioritized based on the value to our broader developer community and the product roadmap. We may not be able to pursue this one immediately, but we will continue to monitor it up to 90 days for community input”
    To add to my other comment… This has killed many good reports I’ve found. I feel like a lot of us give up trying to provide feedback after seeing this a few times. Especially with reports that only affect a minority of VS users (Xamarin, etc.).

    • Mads KristensenMicrosoft employee 0

      I agree, this is terrible wording. What it means is that the suggestion goes in the Under Review state where more votes and comments can be made. Sometimes even design iterations take place in the comments when they are Under Review

  • Daniel Smith 0

    Oh boy what a can of worms to open!  One thing I see a lot, is people getting frustrated that sometimes bizarre changes are made to Visual Studio, or much loved screens or features are ripped out without any requests from the community, and yet some of the highest rated user requests go ignored.
    Obviously you guys need to have the freedom to innovate, but it feels like you could make better use of the blogs to get early feedback on potential changes from a wide range of your real world users, as opposed to using private focus groups.  There’s certainly an abundance of people on here who are more than willing to provide feedback 🙂

    • Mads KristensenMicrosoft employee 0

      Thanks for the comment. Using the blog more proactively is a great idea to gather early feedback. Sometimes design iterations take place on the suggestion tickets themselves, but it would be more visible to do that on the blog.

      • Jakub Suchy 0

        Maybe you could compile list of interesting suggestions weekly and ask the community to vote on some of them with limited votes for each person every weekend. I would gladly subscribe to that!
        It reminds me something simillar to Windows 10 Bug Bash events. Except we would not hunting bugs, but suggestions. Which is in my opinion next level.

    • Chuck Ryan 0

      This is definitely the biggest problem with Visual Studio since 2012. Whatever plan Microsoft is following makes little to no sense to those of us who used to be considered their customers. I know we are tired of having to constantly backtrack and rewrite code because Microsoft decides to ‘upgrade’ something that works and replace it with something that removes core features and adds back nothing new. Microsoft may consider Visual Studio to be moving forward but, for all but their internal development teams, it is moving backwards as all the ‘new’ features are ignored while we constantly fight to fix what their upgrades have broken.

    • Mike Diack 0

      Absolutely. Witness the mess of the start/new project stuff, and the requests to not mess with the VS 2019 IDE (blue now being purple) and the menu bar etc. All of which were MOSTLY ignored.

      • Mads KristensenMicrosoft employee 0

        For what it’s worth, I just released the 2017 version of the blue theme as an extension for VS 2019 called Original Blue Theme

        • Mike Diack 0

          Hi Mads, Credit and thanks to you for this. You’ve done a great job with this. I just tried it. Now let’s get some more of 2019 (and 2017 Update 9)’s issues addressed.

          • Tsahi Asher 0

            Some people just can’t accept changes. I for one did not like the 2015/2017 blue theme, and fixed it using the Color Theme Editor extension to make out of focus active tabs more distinct from the non-active tabs (e.g. when the Solution Explorer is the focused pane). This was improved in 2019. For me, Visual Studio is constantly improving, with only a few things that annoy me. One is the Help Viewer, that became optional (and with the shut down of the documents web service on old MSDN, I also can’t add custom content to it), but I know many of my colleagues don’t bother looking at API docs, and just go to Google. Another is the threat to replace SSDT with with RedGate, which fortunately didn’t materialize yet. Oh, and the old pain of removing and abandoning the Deployment Project back in 2012. So yeah, I don’t like all the changes, but there are more improvements than setbacks.

  • Alexandr Golikov 0

    Agreed with all above.
    What can you say about many times requested 64 bit VS suggestion that bein closed every time? 

    • Wil Wilder Apaza Bustamante 0

      This comment has been deleted.

  • Robert Gale 0

    Every single weekday, the Visual Studio engineering team implements a community submitted suggestion.
    I wasn’t quite sure if this is meant to be good or shockingly slow?

    • Mike Diack 0

      I thought the same. Given that a suggestion might be as little as tweaking an icon or writing a text message in clearer description all the way to a static analysis improvement, I dunno whether to clap or slow hand clap at 1 change per day…..

    • Vincent Thorn 0

      Just count: every single developer works 240 days/year. Making feature every day. (wow!) 🙂 Having even 10 developers MS could make “ideal IDE of all times” (for 15 years!). But they don’t. Too much “below the average” coders, too much “discussions” and very narrow vision of real requirements from real developers.

  • Federico Navarrete 0

    I’d rather focus on the bugs since the current iteration of VS2019 is quite tricky, I have experienced multiple bugs in macOS and Windows every release reaching a point that the question mark is: What is going to the new broken section? Is UWP going to work? Is Xamarin still supported?
    I’d rather focus on improving this part because I’m quite surprised that Microsoft is allowing the release of so many bugs per release, I have been using VS since the v6 to 2019 and I have never experienced so many bugs in one release in 13 years.

    • Mike Diack 0

      Absolutely. Both VS 2019 and VS 2017 Update 8 and later are both buggy. Please fix them before adding new features.

    • Mads KristensenMicrosoft employee 0

      It would be interesting to do a blog post on how we handle the community submitted bugs. We get many more bug reports than suggestions, so there’s plenty of data to dive in to.

  • David Roff 0

    I realise that the default tone for all comments is sarcastic, negative and often rude, but I would like to offer an exception.
    I think that Visual Studio is still far and away the best tool for my C++ developement needs. I’ve tried and discarded many others. Better still, it seems to be improving steadily, with stability and responsiveness leading the way. The newer C++ compiler and CMake support get a big thumps up from me. Sure, I have my gripes, but I can empathise with your team and I realise not all changes will be approved. Surely anyone can understand that not all suggestions can be implemented and there perhaps isn’t time, or resource, to explain why some suggestions don’t make the cut. 
    Keep up the good work.
    P.S. I don’t, and never have, worked for Microsoft

  • Mike Diack 0

    There is too little transparency and accuracy from Microsoft:1) Many regressions in the recent 15.8+ builds of VS 2017 have been flagged. The response has almost always been “it’s fixed in VS 2019, use that”. This has angered MANY people, because the answer is inexact and TOTALLY misses the point – the customers need the fix in VS 2017, which was working but has become broken (these are genuine regressions, not things that never worked to begin with). I have raised this with Nick. ATL wizards broken, #import wrong, wizards creating unbuildable code etc. You as a group need to fix this as well. 2017 Update 9 is intended as a long term support version of VS 2017, but has significant problems.2) When problems are resolved, the details of a fix becoming available are vague (they rarely refer to a build or version number exactly), instead saying “it’s now fixed”. This is hopeless for anyone outside of Microsoft. Why can’t we know exact builds etc that the fixes have gone into?

  • Mike Diack 0

    Agreed – the closure process is terrible. The lack of response beyond “Closed” – is why so many people are so angry with the VS team – because it feels like the much heralded community are having all their feedback tipped in the bin. Frankly it feels like we’re ignored. Many many many people want the start/new project work “fixed”. Many more people said – please don’t mess around with the VS IDE UI (the menu bar etc), but that feedback too, was mostly ignored. Much as with Windows 10. It feels like you are fiddling around with the periphery rather than getting the basics right.

    • Wil Wilder Apaza Bustamante 0

      This comment has been deleted.

  • Sam Jost 0

    What about translation bugs? Should I post wrong translations as “feature suggestion” or is there a bug forum for these?
    For example the new testing dialogue in VS2019 has ‘state’ in german as ‘bundesstaat’, which would be, like, Texas, New York, … which of course is plain wrong.

    • Mads KristensenMicrosoft employee 0

      Yikes, that’s a bad translation. Bugs are reported through the Help -> Send Feedback -> Report a Problem… menu in Visual Studio. Those bugs are opened directly in our bug database.

      • Sam Jost 0

        Yep, it’s one of the worst translations in VS – there are quite a few which are not wrong, but ugly. Like when you copy/past a file in english the new file will have ” – copy” attached to the file name. In german it attaches ” – kopieren”, which is more like ” – copying”. Better would be ” – Kopie”. 

        • Tsahi Asher 0

          I wouldn’t have tried using VS in anything but English, even if it had a translation to my language.

  • James Foye 0

    Lost cause. I myself, after decades of using Visual Studio, switched to Rider. I come here now to the VS blogs because I find comments entertaining. (I have a dark sense of humor). Despite all the protestations of “We are listening”, you continue down the road of changing things for the sake of change, then springing them on the community, then dealing with the negative feedback after the fact, when it’s too late to do anything. Plus at some point you fired too many QA folks, as the bugginess of the product seems to get worse and worse.

  • Scott Ward 0

    I have a suggestion on there that seems to be totally ignored apart from the (I’m guessing) automated first response from Jane Wu
    I submitted a suggestion on 01 May 2019 and its now August so 3 months and no feedback what so ever, apart from non microsoft people with suggestion of how to get a response (those ideas went un-noticed as well).
    It would be nice to have some dedicated people to triage these and have some more status, eg, I can reproduce this issue, any known workarounds or state there is none, Has been added to a wish list that is actually looked at by the developers, under development, etc  
    my post:

    I also aggree with the last commenter about the “controls for writing up features” they are terrible, it mucked up all my enter marks and could not be fixed while editing it. (On that note this page gives me a non-adjustable 4 line control for commenting (using Firefox))
    I love visual studio and use it on a daily basis for work and fun, it would be nice to be heard when there are feasible ideas that would make my and other users experience better and more productive

  • Ladislav Burkovsky 0

    I´m working daily with VS. I can tell you over the years we don’t got have significant improvements. Refactorings are at best basic (MS doesn’t use it internaly ?). Other area are mem/speed profilers. Why can you not integrate(buy) a serious tool. What happend with all the UML Tools (not integrated with class diagram). You are jumping from one theme to another. Take time and money and finish things so you can be PROUD of them.


  • Ondřej Linhart 0

    Instead of fixing some functionality from VS2017, you just remove it in VS2019… Who wants to work in latest VS with less functionality than previous?
    How exactly you measure “little usage by our customers”?

    • Mads KristensenMicrosoft employee 0

      What features are you missing in 2019 that was there in 2017? Perhaps I can help figure out what happened or what to use instead.

      We know what commands are invoked, tool windows used, and other such data points. So, we have very granular data on any part of the product and how much it is being used.

      • Ondřej Linhart 0

        I don’t care about your usage statistics, which is by the way irrelevant, because lot of users have it turned off.
        I care about features that were available in VS2017 and you removed them just because you did not fixed them where they did not worked.
        Save new projects when created option is out, you can easily find how devs are angry about that here or here
        – Horrendous New Project window in VS2019, who asked for that?
        Bug I reported 3 years ago was not even touched
        I can continue, but these are most important ones for me. And your solution to these problems? CLOSED

      • Ondřej Linhart 0

        Save new projects when created option was in 2017 and is not in 2019
        Clearly organised New Project dialog was in 2017 too, is not in 2019

        • Pratik NadagoudaMicrosoft employee 0

          Hi Ondrej – I really appreciate you taking the time to give us feedback. I’m sorry to hear that your original bug was not addressed. We’re working exceptionally hard to address each issue that customers report and you are correct that we need to do better. Please keep sharing your thoughts with us and I hope that you see improvement soon. 

          As Visual Studio is a 20+ year old product, we are intentional about the features that we carry forward to the next major version. In this case, we chose to drop the ‘save new projects when created’ option due to the extremely low usage and high cost to maintain. We’re open to reimplementing this feature if we see a significant number of customers requesting it but, as of now, we do not have that evidence. I hope this helps to clarify.

  • Matt Lavallee 0

    As a long, long time user of VS, what I see affecting my day-to-day has been an apparent fracturing due to trying to satisfy so many personas. I think part of VSCode’s overwhelming success is simply that it doesn’t have that burden.  When you’re an architect working with dozens of repos, dozens of branches, and hundreds of apps, feature changes like the new Start Page — which is probably perfectly fine for 50%+ of VS users who rarely context-switch — cause meaningful loss of productivity every single day.  It’d be fascinating (and helpful) to understand if the program managers are trying to weight the personas equally or if it’s just a question of pure vote volume that represents the community feedback.

  • Jan Heckman 0

    Mads, thanks for the good intentions and I understand limited resources and an overwhelming workload.
    Besides, I like improvements in VS2019, so I’m in a positive mood, so to say.
    Anyhow, given the subject, this cannot be anything else than an intro to some complaining. Sorry.
    It appears to me that your guys can ot upscale properly when a bigger issue is involved. I miss the triage proces.
    See which eventually works out to the (m)idl legacy code using type(def)s which need change because of C++17. This is in the bug department, but I feel the issues are similar. The issue is almost exactly 2 years old (under investigation), there’s plenty of comment and urgency, but all I see is some inane work-arounds and a question whether the issue can be closed, which I downvoted. The issue can imo be resolved fairly easily but requires work by MS. Here, the conductivity from problem to solution is not exactly very high and communcation is virtually absent. Better exampes do exist.
    I’m not happy about using this channel to go into details, but found this really frustrating, after feeling frustrated by (imo) a quite silly bug.These reports are often not made in the best mood and that shows.

  • Ondřej Linhart 0

    Looks like deleting replies is as effective as closing VS issues…

    • Tsahi Asher 0

      This isn’t deleted. It’s right here.

  • Steven Rasmussen 0

    Hi @Mads Kristensen – I’m curious to hear your thoughts on why one of the most voted suggestions (94 votes) with a lengthy discussion was closed.  It wasn’t even asking for new functionality, it was asking for the “old” functionality to be returned:
    Looks like another reason why issues might be closed is due to CYA – In this instance it seems like the MS UX devs don’t want to admit that perhaps their “new” UI design is less than optimal.  All we’re asking for in many instances is the ability to toggle new features on/off instead of things being shoved down our throats.  There’s absolutely NO reason this couldn’t be a toggle on the options page.

    • Mads KristensenMicrosoft employee 0

      I don’t know why that particular suggestion got closed, but I know the team is exploring various possibilities to bring the developer news back into Visual Studio.

      • Steven Rasmussen 0

        That’s great to hear… but if that’s true why is the suggestion related exactly to that “closed”?  It would seem that the suggestion would remain “Open – Under Investigation” or some other appropriate status.  Closing the issue tells me that the decision has been made to stop any further investigation and to just “move on”.  Which one is it?  Is it still being investigated as you say?  Or has MS decided to close the book on this one?

      • Davis, Jon 0

        “I don’t know why that particular suggestion got closed, but I know the team is exploring various possibilities to bring the developer news back into Visual Studio.”
        Then what the heck is this??
        Pratik Nadagouda [MSFT]Jul 11 at 10:54 PM
        ​Thank you for the feedback and comments. At this time, we are closing the suggestion as it isn’t something we are investing in for the near future roadmap. You are free to refer to the news feed in the installer, our website at, or third party marketplace extensions for your news feed.
        You guys need to synchronize internally. This is really quite awful. I mean, awful. And infuriating. That particular thread had a lot of invested minds in interest (along with the suggestion threads showing dismay about the new modal dialog as the Start Page replacement) and that comment by Pratik basically threw the whole thing into the bin. Incredibly disrespectful to your customers.

        • Pratik NadagoudaMicrosoft employee 0

          I’m sorry that you felt disrespected, that wasn’t my intent. We honestly aren’t building anything at the moment to bring a developer newsfeed into Visual Studio. We initially thought of making a news tool window for those who wanted it back but Yann beat us to it with this excellent extension – And I’m happy to recommend that developers use this extension if they want to see the news in their IDE rather than the installer or the web. I closed the suggestion, because we felt that was a sufficient solution. But if there are enough downloads of it to tell us that this is a feature that needs to go into the IDE, then we’ll definitely look into it again.

          • Eugene Ivanoff 0

            Ridiculous! “Let’s remove it in the hope someone will write an extension” policy.

          • Steve Parker 0

            So, my question then becomes… why?  Why did Yann beat you to it?  Why, after stripping such a fundamental part of the startup experience, and every single respondent asking for it to be brought back, why did it take Yann to beat you to it?

          • Pratik NadagoudaMicrosoft employee 0

            Honestly, Steve, we are hearing from many developers that they read their news primarily in the browser or other readers. We have not seen evidence that justified re-implementing a newsfeed and we’re not sure whether it has a place inside of the IDE. While we debated this, Yann went ahead and built the extension 🙂 We appreciate the contributions of our extensibility authors and a customer installing an extension is a much stronger signal for us to consider.

          • Steve Parker 0

            Oh, that’s great!  Visual Commander has had fourty-six THOUSAND installs, so you’re finally bringing back macros, right?
            What does “many developers” even mean?  What about the “many developers” who said they wanted the newsfeed restored? I’m sorry, but what you’re saying is that you’re basing decisions on faulty metrics and our feedback is worthless. Somone else has to write the extensions in order for us to get the value-added features we actually want.

  • Steve Parker 0

    You failed to mention another way that suggestions are handled.
    In the case of anything which criticized the new modal Start Window,  the discussions were completely hidden from view once they started racking up the highest vote counts of any topic.  At first, an attempt was made to dilute the discussion by closing the main thread and scattering people off to different topics.  It didn’t work, so when those topics started gaining votes, they were removed from visibility (some by being moved to an irrelevant thread or re-tagged).
    Even now, the topic “Make the Visual Studio 2019 start window non-modal” is not visible despite it having 53 votes. Of course, removing these topics from visibility ensures that they get no more votes.
    I find the level of censorship disturbing and the level of disrespect disgusting.

    • Pratik NadagoudaMicrosoft employee 0

      There hasn’t been any intentional censorship of topics. The suggestion you’re referring to is still open and under review. We definitely are still looking into options there. I’ll discuss with the feedback team to check if there’s a bug by which topics are not showing up from search. The reason we split up the main thread into sub-suggestions was so that we could actually pinpoint the problems that were being faced and design solutions for the specific issues. We weren’t able to get a measure of what you all were voting on when the suggestion was an amalgamation of several topics. Again, thank you for the feedback and I apologize that you felt disrespected. 

      • Steve Parker 0

        Intentions notwithstanding, that is how it appears from this side.  The question as to why these threads seemed hidden was asked a number of times in a number of different threads.  In fact, the thread we are talking about asks, quite directly, why it seemed like suggestions were being “thinned” and threads seem to be inaccessible from the search.  Being non-responsive only contributes to the problem.  If nothing else, this clearly demonstrates that the current feedback system is broken at a fundamental level. People can’t vote on something that they can’t see.
        There are numerous complaints about ..every.. ..single.. ..aspect.. of the Start Window and the most disliked things about it – modality, no news, and no customization – are the very things that are NOT being addressed or discussed. What committee decided behind our backs not to include dev news after receiving so many votes and every single respondent saying they wanted it brought back? The topic was opened December of 2018. There was zero feedback before it was closed on July 11, 2019. The modal issue has been going on since January! 
        Why bother gathering suggestions if they’re just going to be ignored?

      • Steve Parker 0

        Intentions notwithstanding, that is how it appears from this side. The question as to why these threads seemed hidden was asked a number of times in a number of different threads. In fact, the thread we are talking about asks, quite directly, why it seemed like suggestions were being thinned and threads seem to be inaccessible from the search. Being non-responsive only contributes to the problem. If nothing else, this clearly demonstrates that the current feedback system is broken at a fundamental level. People can’t vote on something that they can’t see.

      • Steve Parker 0

        Testing… since I don’t seem to be able to respond…

      • Steve Parker 0

        Intentions notwithstanding, that is how it appears from this side. The question as to why these threads seemed hidden was asked a number of times in a number of different threads. In fact, the thread we are talking about asks, quite directly, why it seemed like suggestions were being thinned and threads seem to be inaccessible from the search. Being non-responsive only contributes to the problem. If nothing else, this clearly demonstrates that the current feedback system is broken at a fundamental level. People can’t vote on something that they can’t see.There are numerous complaints about every single aspect of the Start Window. The most disliked things about it – modality, missing news, no customization – are the very things that are NOT being adressed or discussed. Which committee decided behind our backs to not restore dev news functionality? The topic was opened December of 2018. There was zero feedback before it was closed on July 11, 2019. The modal issue has been going on since January!Why bother gathering suggestions – suggestions on which everyone seems to agree – if they’re just going to be ignored?

      • Steve Parker 0

        So… every time I post a cogent response to this it gets deleted.  Any idea why?

      • Steve Parker 0

        Finally, after nearly two months, my attempts to respond magically… and suspiciously… appear.

        Now, I would like to know, do all comments “await moderation” or am I now on someone’s black list?

    • Chuck Ryan 0

      At this time I think it is safe to say Microsoft is not dealing with us in good faith. Perhaps it is time to move these discussions to a wider audience and to sites that they cannot censor. We are quite obviously not making any progress here.

      • Pratik NadagoudaMicrosoft employee 0

        Hi Chuck, I am sorry that we have given you that impression. So that I can understand how we can do better, would you be willing to get on a call? My email is prnadago at microsoft dot com.

  • Fawad Raza 0

    So many comments should tell one and only one thing to Microsoft. Your feeback system is severely broken and yes this “Pratik” guy is bit immature in dealing with an issue, it underlines a deeper problem of lack of training in Microsoft about the way things are handled.

    Don’t just say stuff, act upon it too, please.


    • Pratik NadagoudaMicrosoft employee 0

      Hi Fawad, I apologize if my actions have been immature. Would you be willing to have a call to discuss further? My email is prnadago at microsoft dot com.

  • Magnus Mikkelsen 0

    How about adding a pane to the Visual Studio Installer, with links to new suggestions?
    Pick 5 – 7 new suggestions at random, and ask the user: “Which of these suggestions do you like the most?” 
    Or have reaction buttons along with the links. For example: “I need this!”, “But why?”, “Unclear: I don’t get it!”
    I think the data produced by this poll, might help your team to process and rank new suggestions. And it might also make users more aware of the suggestion process.

    • Mads KristensenMicrosoft employee 0

      Now that’s a cool idea. Bring the suggestions more front-and-center so people can better discover them and cast their vote. Just sent an email to the team. Thanks!!

      • Michael DeMond 0

        Did you seriously track a new idea with an email rather than using the system that you posted an entire blog post on, boasting on how you intend to make it better?

        • Mads KristensenMicrosoft employee 0

          No, didn’t track it by email. Made the appropriate team aware of @Magnus’ comment. Come on, now

          • Michael DeMond 0

            Pointing out that you basically spent a couple thousand words claiming that you are “improving” the feature suggestion instrument of your corporation, then directly did not that when presented with a “cool” idea and feature suggestion, is all.

  • Eleven Admin 0

    Consider this highly-voted ticket which is a hugely-annoying bug.  Fixed pending release for two years?!?  Then re-opened through desperation by someone, which was closed but actually triggered no progress on the matter.
    Then this ticket – it’s Closed – Fixed.  But it isn’t fixed.  The “fix” hasn’t worked for everyone.  So that’s the end of the story? 
    These are examples of why we get fed up with the feedback system.  Through goodwill and community spirit we try to help you to make VS better.  But often we’re just ignored once you’re done listening.

  • Andrew Truckle 0

    Another problem is that you are wanting to test issues with “laboratory conditions”. Many times we can’t do this. Like the MFC Class Wizard issues. The only way to resolve those it to include more debegging log info or to remove it to our particular projects. So many of my problems are closed because I can’t help you reproduce the issue. You need to try my particular projects (which are GBs is size etc.) and provide advanced error logging to produce sensible errors so that you can hone in to the real problems.
    Whilst i appreciate that VS 2019 is provided free, it is not really my responsibility to beta test the application. It should have already been tested with real life programs that started out in VS 6 and have migrated through VS2005, VS2015, VS2017, VS2019 to there they are now.

  • Andrew Truckle 0

    People also often add “replies” as “answers” which is wrong. And using your site on a mobile is very difficult. I have to use a PC for it to be a easy user experience.

  • DragonSpark 0

    You all put something “Under Consideration” and then mark it for closure 60 days later? whut?
    Also, do you all actually enjoy making counter-intuitive user interfaces now or are you there just to collect a paycheck these days and chalk it up to something Google would do?  All of the above?

  • Jon 0

    As many others have covered, the feedback and bug-reporting UI/UX is terrible, using the lack of votes to close good suggestions and valid bugs is ridiculous (who has time to wander that terrible site tossing around votes?), but the reason I’ve stopped using the site is when a valid bug is closed either because nobody got around to working on it, or worse, somebody arbitrarily decides it isn’t a bug. A prime example is this bug I reported where simply running VS continuously generates a ton of errors in the event log. Somebody (probably an intern or contractor judging from the inept answer) pops in to post irrelevant junk he randomly Googled (he literally writes “I looked up these error codes on the internet”) then closes it, probably one ticket closer to his daily quota. Guess what? It still happens in VS2019. This was the straw that broke the camel’s back for me. I haven’t reached the point of giving up on VS yet, but I’m done helping you debug your product.

  • Mike Diack 0

    I’ve said it elsewhere, but having looked at how this thread is expanding I went and looked at some of the bugs people raise. A few trends are very clear.1) Versions that a fix is in are rarely clear – the answer is often “fixed in latest release”. For the love of God, please put the version number in – surely it can’t be difficult for support staff (or the bot that does it), to put the version number of the fix in?2) Too often, the replies are just verbatim that could be written by a robot, and are more like a press release/lawyer – “your feedback is important” etc. and convey no useful information.
    3) As others have mentioned there have been important bugs floating around for 2-3 years, in a weird state of limbo (open, but not closed, fixes working for some people not others, lots of “me too” or “still broken in version ……” . Surely you can do better than this. Its just a mess. But my main bugbear is 1 and 2.

    • Mads KristensenMicrosoft employee 0

      All valid points

  • Mike Diack 0

    One practical piece of advice for others posting here – email John Montgomery and/or Nick Uhlenhuth with your issues – once I started bugging them directly via email with examples of the mess that VS 2017 and the bug reporting/follow up/tech support process is, things started to happen.

  • John B 0

    The biggest frustration is that first responses are from people who jump straight to “need more info” even for simple reports. It gives the impression they’re not versed in the technology, aren’t taking time to read, or lack communication skills.

    • Chuck Ryan 0

      Yeah, they love to give you a research project to figure out what the problem is in their product and then act suprised when you ask where to send your billable hours.
      Do they think we work for free?

  • Neil MacMullen 0

    Well, I’ve just had yet another issue-report closed with the standard “lack of activity” template reply.  I really do appreciate the necessity to prioritize and the reality of finite development resource but I’ve now reported several genuine bugs (at the the very least, undesirable behaviours) that have been ignored this way.  In the development teams I’ve run, we always treated customer reports as an important feedback mechanism to uncover bugs that had escaped internal testing and actively chased these up rather than just waiting to see if more than one customer would notice.  (On more than a few occasions a ‘minor’ behavioural oddity turned   out to be an indicator or something potentially far more serious.)  I don’t know whether the issue is just that the people doing the triaging are primed to try and ‘protect’ core development but I’d echo a few of the other comments here that the impression I generally get is that the triage process seems to be heavily biased towards rejection – both of false reports and genuine ones.  Often there is a request to provide infeasible amounts of supporting evidence (yes – we all want a local repro case – I understand!).  I can’t just hand over my entire solution (or PC!) but in the past I’ve offered to run test builds to capture problems and never been taken up on it.  Anway, I really do hope things improve.  Visual Studio is still actually a great product and I have very few gripes with it  but the feedback process is an exercise in frustration and I’m inclined to stop providing feedback since the vast majority is rejected.

    • Chuck Ryan 0

      Yeah, same here. The only response I received to my report was from Jane Wu saying they were shutting it down as low priority since there was no redeeming activity or whatever… that was my last attempt at a bug report as I have no interest in wasting my time. Although I must admit some suggestions have great comedic value. I call this one Pratik’s one man show:

      • Neil MacMullen 0

        ha-ha -that’s great! I guess there are some perks to working on the dev team 😉 

  • Mike Diack 0

    Continuing my comments about the terrible feedback loop on bug reports (specifically identifying which “latest release” has the fix, by absolute number, rather than just saying “Fixed in latest release” (at the moment that the Microsoft staff member wrote the bug report update!)Perfect example:The following bug was fixed in this week’s Visual Studio Update 9.15 patch:
    Release notes here: on that bug report, does it make ANY mention of a fix being in the 15.9.15 update?

  • SuperCocoLoco . 0

    Microsoft is clearly ignoring his user base feeback, suggestions and bug reports. Reporting suggestions or bug are a waste of time.
    The best thing to describe this is all suggestions post about the “New Project” window dialog. There are pages with posts about this in the developer community claiming for restoring the old tree-based “New Project” window dialog and also ensuring that it is the worst thing Microsoft has done in Visual Studio since 1997. Also some posts have a lot of votes and comments.
    But the only answers from Microsoft are they are “improving” the “New Project” window dialog adding more filters, more search options that absolutely nobody has claimed. Users are only requesting and reclaiming the older TREE-BASED new project dialog. But Microsoft clearly said that do not restore the old tree-based window dialog never again, ignoring, angering and infuriating his entire user base.
    But not only not restoring the old tree-based new projhect window dialog, they are also removing in 16.3 the underlaying code that allow thrid party extensions to use that good features that users reclaims, like the old “New Project Dialog” and the old “Start Page” for more angering and infuriating your entire user base.

    Why is Microsoft ignoring feedback and user base? What about transparency? Why Microsoft not admit how bad do it with the “New Project” dialog, the new “Start Window” and the new “Compact Menu”?
    More things of posting in developer communty are a lot of post that Microsoft changes the title, like my title`aprox. “Allow to show the complete Title Bar option” in Visual Studio 2019.0 preview changed to “Fix usability issues in compact menu bar” that is not the same thing and has nothing to do with my suggestion, because i have no interest in compact menu and don’t want Microsoft fixes any issues, i only want the real and full Title Bar like any other application. In the last minute Microsoft added that option in the final version.
    More things are closing posts and suggestions as duplicate, linking to other suggestions that has nothing to do and are clearly not the same.
    More things are a clearly and reproducible bug in Visual Studio 2017.0 WPF editor, that changing the name of a control produce a lot of errors because code not find the old name of the control and closed because didn’t receive any votes. Finally fixed more than a year later in 2017.9 aprox.
    The way Microsoft handle suggestion is an horrible mess, not really hearing his user base feedback and clearly a waste of time. I will never report any suggestions or errors ever again.

  • moovthis 0

    I don’t think this is necessarily a problem with the feedback system. My thinking is that there are underlying causes.
    First the culture at Microsoft is to come up with new and more efficient means to do stuff. Understood. The end users want a stable, bug free and fast development platform (and the tooling that goes with it) that is around for a long time AND has a low cost of ownership. For my purposes the Community Edition works just fine so the initial cost of the product is fine (i.e. free), but I measure my time wasted on what I describe here in hours and sometimes days. And so far I have stuck with a single development platform and as such have avoided months, maybe a year of my time redoing my code because of the new flavor of the year platform from Microsoft. 
    Second, a lack of understanding how Microsofts customer’s use case is different. Microsoft is working on a product but the end users buy a tool. I think that means that the knowledge about the product at Microsoft has to be at a higer level than the users of the tool. As result minor changes made by Microsoft often times result in problems for the users that take a significant effort to resolve. I have several examples but this one is very typical. Some functionality got added, causing thousands of exceptions that prevented me from building and deploying my code and several hours of my time to understand what this was about and how to fix it. More recently, Microsoft thought it was prudent to remove a registry key in my VS2017 install when the 16.2.3 update to VS2019 gets installed. That totally effed up EF in VS2017 and again several hours of my time down the drain. Someone should have considered the consequence of turning on this feature. In addition consider those updates that are forced down our throats at the most inopportune moments where the functionality of the machine at the very least is severly degraded at worst unusuable.
    Third, there has to be someone to put a stop to hare-brained ideas, to nip things in the bud, an adult in the room. Let’s take the debugger step icons in VS2019 as an example. Someone took something that worked and probably no one was complaining about and changed it into something that was regressive in nature and resulted in complaints and jokes (in general about the Microsoft icon do-over). I am thinking this is an example where the adult in the room should have acted and the responsible persons punished (no use of smileys and emojis for a month?).
    From my perspective I cannot rationalize the things I see happening with Microsoft except to think Microsoft does not use their own software (like I do) and that there is a large quantity of kid coder employees who have no clue of the consequences of their actions, and a shortage of adults in the room.
    I cope with this dichotmoy by laughing out when the latest Microsoft blog post comes around and explains code efficiency improvements measured in seconds, new icons, glowing stories about emojis, smileys, transparency and like buttons.  Of course sharing the pain helps with coping so I have bi-weekly sessions with developer friends where we exchange the lastest frustrations with Microsoft. 
    I wish for Microsoft to consider the total cost of ownership of their products and act cautiously as to not waste our time. The issues with the feedback system are a result of some of the issues I have addressed. 
    This is just my opinion, I could be wrong.

  • Michael DeMond 0

    Another dubious example of “improvement.”  You ask users to provide information with a feedback tool, which takes many minutes to complete.  And THEN when the issue is “triaged” you further ask the user to jump through MORE hoops to collect more information, that for some reason was not collected in the first place?!  Worth noting that JetBrains was able to fix an issue with the provided collected information whereas MSFT cannot.  *shrug*

Feedback usabilla icon