Closed
Bug 316420
Opened 19 years ago
Closed 18 years ago
Ability to vote for/set #1 bug in bugs tracked
Categories
(Bugzilla :: Bugzilla-General, enhancement)
Bugzilla
Bugzilla-General
Tracking
()
RESOLVED
DUPLICATE
of bug 147786
People
(Reporter: scunliffe, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7
A Feature Request to include the ability to flag a tracked bug, as one's personal #1 bug.
This is in addition to regular voting.
As a user, I would like to be able to identify to the system/engineers, that bug: [#xyz] is my #1 bug. E.g. That I see this bug, as the most important, to me, to get fixed.
The end-user, would only be able to select one (1) of their tracked bugs, thus being able to identify to the system, what is of most importance to them.
Likewise, if the system could provide means, to display info on this, it would be excelent.
E.g. (when viewing a bug)
Votes: 874
Users that rated this their #1 bug: 59
As a result, it would help the engineer/developer, instantly see, not just how many people noticed this bug, but how important fixing it is.
Reproducible: Always
Steps to Reproduce:
1. Feature Request only
Expected Results:
If possible, when viewing a "grid" of bugs:
Bug# | Desc | Votes | User Voted #1
-------+---------+------------+----------------
47262 |Contr... | 437 | 13
57178 |Syste... | 12934 | 238
837542 |User... | 8653 | 511
39282 |Inter... | 9232 | 4
With something like this, one can see that although 12,934 votes were made for bug 837542, bug 837542 has 511 users, flagging this as their #1 bug to be fixed!
Which, for a developer trying to decide what to tackle next, should be very helpful info in determining what the user/customer wants.
The idea for this, was inspired on a Mozilla - Bugzilla thread, that although receiving lots of votes, isn't/wasn't receiving any attention.
Comment 1•19 years ago
|
||
This is what voting was originally intended for. Then everyone complained that you couldn't vote enough times and wanted more votes per-product. Eventually the QA folks gave in and upped the vote limits to something ridiculous, and now a vote doesn't seem to mean much anymore....
I think this is a good and effective idea.
People will complain less in the comments, as they will be able to express their frustration in a clear and more efficient way. This will both reduce the spam and help developers see how many people are "really really" desperate to have the bug fixed.
Comment 3•19 years ago
|
||
I disagree that this would be effective. If developers currently ignore votes, having some other votes figure will be ignored as well.
Personally, I work on stuff that I want/need/find interesting. Don't care about votes at all.
The voting implies your vote means something, it does not. The complaints are because of that (and I can understand it causes frustation). I think voting is useless, perhaps it can be made better by renaming voting to something else, but having it turned off completely works for GNOME (coupled with a gnome-love keyword so developers can specify what bugs are wanted / easy to fix and that they will assist a contributor).
Comment 4•18 years ago
|
||
I also strongly suggest to WONTFIX this bug.
*** This bug has been marked as a duplicate of 147786 ***
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•