Overview: Suggest a Feature
We've introduced a brand new experience for suggesting features alongside the current ability to report problems on Visual Studio Developer Community. This is a new way you can be empowered to engage directly with Visual Studio’s engineering workflow.
Until now, Visual Studio users have used the User Voice forum to propose new feature ideas. The Suggest a feature experience in Developer Community allows you to transition from the User Voice forum into a single platform for all your feedback that engages directly with the Visual Studio product teams.
We've migrated an initial set of ideas from the User Voice forum to Developer Community. Migration was done based on the community impact of the feedback and our product roadmap priorities. If you were expecting to see a suggestion here that we may have missed, feel free to add it to Developer Community.
The voting system in User Voice operates differently from the votes in the Developer Community. To maintain the integrity of Developer Community vote counts and to avoid skewing of votes, we show the User Voice vote counts prominently as a tag next to each feature suggestion. As you continue to vote on suggestions in the enhanced Developer Community, your new vote counts will show separately from the User Voice vote counts.
The User Voice site is now read-only, allowing you to look back as you need to for context. All new feature suggestions should be submitted on Developer Community.
After you submit a feature suggestion, states indicate where your feature submission is in its lifecycle. As we take your feedback into consideration and move it along the workflow, we tag it with the corresponding state.
The various states associated with feature suggestions are listed below, along with a description of their meaning and color indicators.
New means the suggestion has been newly reported from you or someone else. No action has been taken on it yet. The front line will do some preliminary checks to make sure we can proceed further. Expect to hear from us in about five business days with our next steps.
Under Review indicates that the feature suggestion has been queued up for prioritization. We prioritize features to bring our broader developer community the best value, also taking the product roadmap into consideration.
Even if we're unable to pursue your new feature suggestion immediately, we'll continue to monitor your idea for about 90 days, let the community weigh in, and then make a decision on the next steps.
On Roadmap means that your feature suggestion has a broad community impact and will help improve the product experience. We've allocated time for it on our roadmap. We'll update you on the progress.
A feature suggestion marked Need More Info means that we need more details so we can better understand your suggestion. Check the comments, where we'll ask for additional information to get a deeper understanding.
Closed - Other Product means we're unable to address your feature suggestion at this time because it's not applicable to the product it was reported for. However, we'll provide details on where you can share your new feature suggestion for the appropriate product.
Closed - Duplicate indicates that someone else has already suggested the same feature. Review the comments to find the link to the existing feature suggestion. Votes and comments have been merged in the original suggestion. Follow the original suggestion.
Closed - Not Enough Info indicates that after several attempts, we haven’t received enough information to understand your feature suggestion fully. We have to close the new feature suggestion as we're unable to take any further action at this stage.
Found the information we were looking for? You may request to reactivate the ticket when you have the additional information.
Completed - Preview indicates that we implemented the feature you suggested. You can download a preview version of Visual Studio that contains your suggestion using the link provided in the comments.
Completed - Release indicates that your new feature suggestion has been released in the latest product update. The Visual Studio update can be downloaded using the link provided in the comments.
Why can’t I see my User Voice idea in Developer Community?
New feature suggestions from the old User Voice forum have been migrated to Developer Community based on the impact to the broader community and our product road map priorities. If you think we've missed migrating your suggestion, add it as a new suggestion to Developer Community.
Why have the votes not been carried over from User Voice?
The voting system in User Voice operates differently from the voting system in Developer Community. In the new system, we want to maintain the integrity of the vote counts and avoid skewing the data. We decided to show the User Voice vote counts prominently as a tag (instead of votes) for each suggestion. When users vote on suggest a feature submissions using Developer Community, the new votes will show separately from the User Voice votes.
Where can I see comments associated with the suggestions imported from User Voice?
Follow the link we've included to go back to the User Voice comments on a suggestion that has been migrated to Developer Community. This link will be available during the transition period for easy reference if you need more context.
Why can I see three vote counts for a suggestion?
When a suggestion has been imported from User Voice, you'll see three separate vote counts. The two vote counts shown as tags are the vote counts that the idea received originally on User Voice. The third vote count displayed to the left of the suggestion lets you see how many votes the suggestion is getting from Developer Community.
The voting system in User Voice operates differently from the votes in Developer Community. To maintain integrity of Developer Community vote counts and avoid skewing the data, we decided to show the User Voice vote counts prominently as a tag (instead of votes) for each suggestion.
How long can I expect actions to take?
We're fully committed to listening to your feature suggestions and taking actions to provide valuable experiences to our customers. Actions on suggestions are prioritized based on impact to the broader community. Even if we can't respond personally to every suggestion, we'll make sure that your feedback gets to the right team and is evaluated carefully.
The response time depends on the status your feedback is in. Please review the explanation of statuses in this document to understand the response times.