Closed Bug 260494 Opened 20 years ago Closed 12 years ago

Allow for more precise voting for bugs/features

Categories

(Bugzilla :: Creating/Changing Bugs, enhancement, P4)

enhancement

Tracking

()

RESOLVED WONTFIX

People

(Reporter: WISD00M, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (compatible; Konqueror/3.2; Linux) (KHTML, like Gecko)
Build Identifier: 

allow voting for bugs based on preferenece level by users,like: 
1: would be nice to have/see fixed 
5: urgently required 
 
That way, voting will become more representative and precise. 
 
 
 

Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Status: UNCONFIRMED → NEW
Component: Bugzilla-General → Creating/Changing Bugs
Ever confirmed: true
OS: Linux → All
Hardware: Other → All
Summary: allow for more precise voting for bugs/features → Allow for more precise voting for bugs/features
Assignee: justdave → create-and-change
QA Contact: mattyt-bugzilla → default-qa
An IT organization I belonged to used the following scale of voting for approx
30 years. It includes the use of bug 164310.  

+3 I must have it now - we'd save tons of money !!!
+2 I like it, I want it
+1 I like it
 0 No feelings either way
-1 Not good
-2 Not good, actually a bad idea
-3 Really bad - harmful to my business !!!
 (Please stand and explain to the audience why you're voting this way)

Being a professional organization, voting was naturally expected to be based on
real business case/technical reasons (at least in the case of +3, +2 and -2,
-3), not mere personal opinion.  Badly needed items quickly become apparent by
the vote (eg averages above or approaching 2, with few or no negative votes). 
Likewise, potential pitfalls were quickly apparent by the presence of many
negative votes, or even one -3 vote.  All -3 votes had to be explained by the
voter, and -2 voters were encouraged to so the same.

Negative votes, eg starting at -3, are used because it's easier for the voter to
remember/understand how they are voting than starting at 1.

The scale could be shortened/simplified to -2...+2
Hi Wayne, thanks for your email - yes still around - occassionally :-)

I really like your suggestion, this would certainly come in very handy to
actually evaluate polls.

On the other hand, it might also be worthwhile to consider different voting
groups, i.e. one for "users" and one for "developers", different criteria may
apply, too.

For example, users may be mainly concerned with usability, whereas developers
would also be interested in the complexity or feasibility of a certain request.

regards

Mike
Priority: -- → P4
As negative votes are mentioned here, adding dependency on bug 48570
Depends on: 48570
We won't implement groups or categories for votes. You should tag bugs instead.

Also, in bug 48570, I'm going to allow only one vote per user per bug as the voting system is always abused by people who want to see their bugs fixes.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.