{"id":216686,"date":"2018-10-09T10:00:32","date_gmt":"2018-10-09T17:00:32","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/visualstudio\/?p=19295"},"modified":"2019-02-14T15:23:30","modified_gmt":"2019-02-14T23:23:30","slug":"introducing-suggest-a-feature-in-developer-community","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/visualstudio\/introducing-suggest-a-feature-in-developer-community\/","title":{"rendered":"Introducing \u2018Suggest a Feature\u2019 in Developer Community"},"content":{"rendered":"<p>Customer feedback is a critical input to help us improve Visual Studio. Up until two years ago, the Visual Studio customer feedback system left room for improvement \u2013 customers could use the \u201csend a smile\u201d feature in Visual Studio, but this would result in only coarse-grained feedback such as \u201cI like this\u201d or \u201cI don\u2019t like this.\u201d The feedback we got through this UI then went into a database our team accessed, but didn\u2019t leave an easy way for customers to see the feedback that other customers were giving so they could say, \u201cI have that problem too!\u201d More than that, the back-end system that gathered feedback was separate from the engineering systems we use for tracking bugs and features, crash reports, hang reports, and telemetry. Without a unified system on the backend, identifying the most impactful issues could be an error-prone job.<\/p>\n<p>In Visual Studio 2017, we introduced a new system for reporting issues. From within Visual Studio, users can Report a Problem; the issue is tracked in a public system at <a href=\"https:\/\/developercommunity.visualstudio.com\" target=\"_blank\" rel=\"noopener\">https:\/\/developercommunity.visualstudio.com<\/a>, and the public issue is integrated directly into our engineering system. Thus, a bug on Developer Community is a bug in our Azure DevOps work item database, and votes from the community would give items additional weight.<\/p>\n<p>Since introducing this system, we have received over 70,000 issues from more than 24,000 customers. We have resolved over 13,000 of them, and in over 5,000 instances of issues customers have unblocked themselves quickly using the solutions and workarounds contributed by Microsoft and the larger community of developers.<\/p>\n<p>Until now, we\u2019ve focused the system on issue tracking, but that\u2019s left a gap in our understanding of what customers want from us and developers need: the ability to ask for features. Today, we\u2019re announcing that the same system that we use for reporting issues will work for feature requests in one convenient place.\u00a0 If you have an idea or a request for a feature, you can now use the new <a href=\"https:\/\/aka.ms\/vs-suggest\" target=\"_blank\" rel=\"noopener\">Suggest a Feature<\/a> button (shown below) on Developer Community and make your suggestions.<\/p>\n<p><a href=\"https:\/\/aka.ms\/vs-suggest\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" class=\"alignnone size-full wp-image-19305\" style=\"border: 1px solid #eeeeee\" src=\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/4\/2019\/02\/suggestafeature.png\" alt=\"\" width=\"1397\" height=\"543\" \/><\/a><\/p>\n<p>You can also browse suggestions from other developers and <strong>Vote<\/strong> for your favorite features to help us understand the impact to the community.<\/p>\n<p><a href=\"https:\/\/aka.ms\/vs-suggest\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" class=\"alignnone size-large wp-image-19315\" style=\"border: 1px solid #eeeeee\" src=\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/4\/2019\/02\/featureitem-1024x228.png\" alt=\"\" width=\"879\" height=\"196\" \/><\/a><\/p>\n<p>If you are wondering how feature suggestions are considered for inclusion on our product roadmap, please see our <a href=\"https:\/\/docs.microsoft.com\/en-us\/visualstudio\/ide\/suggest-a-feature?view=vs-2017\" target=\"_blank\" rel=\"noopener\">suggestions guide<\/a> that clarifies the states used to track progress and what each state represents in the journey.<\/p>\n<p>As part of this work, we will transition from UserVoice as the primary means for our customers to request features. The reason we\u2019re moving from UserVoice is very similar to the reason we moved away from the old \u201csend a smile\u201d system: we want customer feature requests to be directly integrated into our core engineering system so we have complete line of sight into the feedback customers are giving us.<\/p>\n<p>Moving off UserVoice is a big job: It tracks 32,000 feature requests and more than 24,000 points of\u00a0 feedback. In unifying our system under Developer Community, these massive number of requests will benefit from a strong systems to help us analyze and track these important requests.<\/p>\n<p>Over the coming months, we\u2019ll be migrating many existing UserVoice items from UserVoice, starting with a few hundred, although tems with relatively lower vote counts and items that are exceptionally old may not move over. Please see these <a href=\"https:\/\/docs.microsoft.com\/en-us\/visualstudio\/ide\/suggest-a-feature?view=vs-2017\" target=\"_blank\" rel=\"noopener\">frequently asked questions <\/a>for more details on how UserVoice votes and comments are being handled.\u00a0 I recognize that may cause some frustration and I apologize in advance.\u00a0 I\u2019d simply ask you to sign into Visual Studio or go on the web and submit the item again.<\/p>\n<h2>Thank you!<\/h2>\n<p><em>Suggest a Feature<\/em> on Developer Community is aimed at providing a single convenient place for all your Visual Studio feedback, improve your engagement with product teams and have a greater impact on Visual Studio family of products.\u00a0 We are looking forward to hearing your suggestions.\u00a0 To reiterate in closing, please visit <a href=\"https:\/\/aka.ms\/vs-suggest\" target=\"_blank\" rel=\"noopener\">Developer Community<\/a> and send us a suggestion.\u00a0 We also encourage you to <a href=\"https:\/\/review.docs.microsoft.com\/en-us\/visualstudio\/ide\/suggest-a-feature?view=vs-2017\" target=\"_blank\" rel=\"noopener\">learn more about suggestions<\/a> to get the best out of it.\u00a0 Thank you for the valuable feedback you provide in Visual Studio and participation in Developer Community!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Customer feedback is a critical input to help us improve Visual Studio. Up until two years ago, the Visual Studio customer feedback system left room for improvement \u2013 customers could use the \u201csend a smile\u201d feature in Visual Studio, but this would result in only coarse-grained feedback such as \u201cI like this\u201d or \u201cI don\u2019t [&hellip;]<\/p>\n","protected":false},"author":585,"featured_media":255385,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1085,155],"tags":[354,1229,12,280,452],"class_list":["post-216686","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cloud","category-visual-studio","tag-announcement","tag-devcomm","tag-visual-studio","tag-visual-studio-code","tag-visual-studio-for-mac"],"acf":[],"blog_post_summary":"<p>Customer feedback is a critical input to help us improve Visual Studio. Up until two years ago, the Visual Studio customer feedback system left room for improvement \u2013 customers could use the \u201csend a smile\u201d feature in Visual Studio, but this would result in only coarse-grained feedback such as \u201cI like this\u201d or \u201cI don\u2019t [&hellip;]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts\/216686","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/users\/585"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/comments?post=216686"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/posts\/216686\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/media\/255385"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/media?parent=216686"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/categories?post=216686"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-json\/wp\/v2\/tags?post=216686"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}