How does Microsoft determine priority of customer submitted bugs and suggestions?

It’s simple, we let the customers tell us the priority of the issue. We’re basing the priority value on the customer average rating and number of votes. Here’s an example:


Priority 1: Average vote value is 4.5 or higher and 6 or more people have voted on the issue.

Priority 2: Average vote value is 4.0 or higher and 3 or more people have voted on the issue.


So we encourage customers to honestly on bugs and suggestions so we can focus on the most important issues first and the smaller issues later.


Marie Hagman

Visual Studio

Program Manager

Comments (5)

  1. Alex Kazovic says:

    Unfortunately, there is no way to vote against a suggestion. For suggestions the range should be -5 to +5

  2. Marie Hagman says:

    Actually you can vote against a suggestion… Voting a 1 on a suggestion means:

    "Implementing this suggestion would negatively impact the product and my experience. Please do not implement it."

  3. AT says:

    Priority 0: Any feedback related to Product Feedback web-site.

    Take a read this:

    "When I (Joel Spolsky ?) reported bugs in Netscape 2.0, the bug reporting website repeatedly crashed and simply did not let me report a bug (which, of course, would have gone into a black hole anyway). But Netscape doesn’t learn. Testers of the current "preview" version, 6.0, have complained in newsgroups that the bug reporting website still just doesn’t allow submissions. Years later! Same problem!"


  4. Alex Kazovic says:

    Marie, unfortunately voting 1 doesn’t allow me to express my level of disagreement with implementing a suggestion. Some suggestions I only slightly disagree with, whilst others I feel very strongly against.

  5. Ryan Lamansky (Kardax) says:

    When voting is not enough, use comments 🙂

    A strong argument has more influence than the votes. This isn’t a democracy.

Skip to main content