Issue 69811 - Allow more votes per component
Summary: Allow more votes per component
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: Bugzilla (show other issues)
Version: current
Hardware: All All
: P4 Trivial with 9 votes (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Keywords: oooqa
Depends on:
Reported: 2006-09-24 14:01 UTC by troodon
Modified: 2013-02-07 22:35 UTC (History)
1 user (show)

See Also:
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description troodon 2006-09-24 14:01:23 UTC
I think allowing more votes per component should be considered, at least for the
five main components for the final user: Database, Drawing, Presentation,
Spreadsheet and Word Processor.

As their complexity and funtionality grows and the userbase also grows, there
will be more and more bugs that people would like to nominate through voting.

Mi suggestion is to go from 5 votes to 10 or even 15.
Comment 1 aziem 2006-09-24 17:58:18 UTC
In the same way that developer resources are scare, so should be votes.   I
suggest not increasing the limit except maybe for people who are QA volunteers,
developers, so perhaps "points" can earn votes.  At Gnome's , they use a point system .

In any case, I do not see much of a correlation between votes and allocation of
Comment 2 ace_dent 2006-09-24 18:33:23 UTC
+2! ;-)

I try and do my bit for QA, and the voting system is useful not just for
developers to track demand, but also for those who do QA to track Issues of
interest (a quick bookmarking method).
I would love to see 10 votes (vs 5), since I never have enough! Earning them
might be handy, but IMHO not worth the developer effort. Give people ten votes-
what's the worst that could happen?

Comment 3 gtimur 2008-12-22 17:38:32 UTC
I vote for this, because I keep finding new issues. There might be also
restriction to use 2 votes only once, if possible.
Comment 4 gtimur 2008-12-22 17:40:05 UTC
I vote for this, because I keep finding new issues and then delete more
important ones hoping that they will be fixed anyway. But, I can't track them
any longer. There might be also restriction to use 2 votes only once, if possible.
Comment 5 meywer 2009-01-05 20:38:10 UTC
I sometimes would like to vote for new issues, but often the older ones, I voted
for, aren't still fixed. Now I come in conflict with the restriction to 5 votes
per component. I don't want to delete my votes for the older issues but I can't
put new votes...

Maybe a restriction to not set more than n votes in one month or in one year or
something like that could be useful instead.
Comment 6 stx123 2011-03-23 16:13:41 UTC
Reset QA Contact to new default