154635 - [RFE] Rate Bug Interest

Status: RESOLVED DUPLICATE of bug 77472

(Bugzilla :: Bugzilla-General, enhancement, P4)

Description

[Jerry Baker]

Summarizing the interest of Bugzilla members in a particular bug may be able to 
give those wishing to contribute a more accurate picture of what bugs are 
considered important to the community. I propose adding the number of CC's, 
duplicates, votes, and MAYBE number of comments into an "Interest" score. Using 
such a technique we would see some different results for bug interest than the 
current voting system allows. The voting system is inadequate because as the 
bug list grows, the number of votes one may cast does not. Take these bugs for 
example:

Bug 91662 would have an interest score of 218 (20 votes, 95 comments that are 
not "marking duplicate", 40 duplicates, and 63 CC's), but it only has 20 votes.

Bug 22687 - 760

Bug 28327 - 418

I think this would give a more accurate picture of what bugs are important to 
the community at large.

Comment 1

[Bradley Baetz (:bbaetz)]

But thats what votes are for. Every so often someone files a bug on m.o wanting
the votes/bug limit to be increased, and asa/myk do queries to show that the
vast majority of people aren't using the current limit

See bug 114767 and dupes.

Given this, I don't think calculating an 'interest level' by adding unrelated
numbers together is a good thing.

Comment 2

[Jerry Baker]

They are not unrelated in the sense that they show interest. People don't sign 
up for the CC list if they are uninsterested, people don't file bug reports if 
they are uninsterested, and people don't make comments if they are uninterested. 
People may, however, be interested in a bug and not vote for it. As far as I 
know votes are not automatic whereas the other indicators I proposed are. This 
way you don't have to rely on people telling you what their preferences are 
because it will be automatic.

Comment 3

[Jerry Baker]

Two identical typos. Uninsterested = uninterested.

Comment 4

[Jouni Heikniemi]

I agree with bbaetz: the cc list thing doesn't work, at least not as such. While
it might be possible to devise a formula that would work decently on bmo, making
one for all Bugzilla installations is impossible.

The proper solution is to implement custom weight-based sorting criteria.
There's a bug on that but I'm too lazy to search for it now. Combined with bug
69000, BZ admins could then create customized weighted queries like "Most wanted
by our community" which could take any factors into account - including
installation-specific keywords and such, which are often a very important
indicator of a certain bug's severity.


Don't get me wrong: I think you're aiming at the correct thing, but IMO the
solution you presented is not sufficiently generic and flexible to fit into the
Bugzilla codebase.

Comment 5

[Dave Miller [:justdave]]

Reassigning all of my "future" targetted bugs to indicate that I'm not presently
working on them, and someone else could feel free to work on them. (sorry for
the spam if you got this twice, it didn't take right the first time)

Comment 6

[mental]

Can we resolve this?  DUP of bug 77472?  WONTFIX?

Comment 7

[Ran]

*AND* looks like a reward for duplicates...

Comment 8

[Dave Miller [:justdave]]

sure.

*** This bug has been marked as a duplicate of 77472 ***

Comment 9

[Dave Miller [:justdave]]

clearing target on bugs with resolution other than FIXED so they'll show up as
untriaged if they get reopened.