Ranking bugs/suggestions by average score*number of votes is wrong and we want to fix it. The solution I propose would allow for tracking of several buckets of bugs and suggestions. Ideally the PFC should have a robust statistics area showing various interesting metrics and the home page should be dynamic and rotate the buckets displayed.

 

First to define what the rating scale should mean for bug vs. suggestions:

Rating

Bugs

 

Rating

Suggestions

1

Fixing this issue is not important.

 

1

I don’t like this suggestion. Don’t waste time implementing it.

2

This is a minor bug.

 

2

I’m neutral, I don’t care if Microsoft implements this suggestion.

3

This bug should be fixed but I can live with it.

 

3

This is a good idea.

4

This bug is very annoying and I want Microsoft to fix it.

 

4

I really like this suggestion, I think Micrsoft should implement it.

5

This bug is very serious, embarassing or it’s a blocking issue. It should absolutely be fixed.

 

5

This is a must-have feature and Microsoft should absolutely implement it soon.

 

Most important bugs

Most important bugs should be determined by the average vote value and ties broken by highest number of votes. To appear on the top ten list, a bug must have at least N votes (where N is at least greater then 2).

 

Best suggestions

Similarly to important bugs, best suggestions should be determined by the average vote value and ties broken by highest number of votes. To appear on the top ten list, a suggestion must have at least N votes (where N is at least greater then 2).

 

Most popular bugs

Determining the most popular bugs should take into account number of votes and validations.

 

Most popular suggestions

Determining the most popular suggestions should take into account number of votes.

 

Low traffic bugs and suggestions

Bugs and suggestions that have fewer then 3 votes or validations should appear on a list where they can receive higher visibility

 

Marie Hagman

Visual Studio Core Team