Closed
Bug 65801
Opened 24 years ago
Closed 17 years ago
Allow "pending" votes or weighted votes.
Categories
(Bugzilla :: Creating/Changing Bugs, enhancement, P5)
Bugzilla
Creating/Changing Bugs
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: mozilla-bugs, Unassigned)
Details
Currently, once a bug is resolved, people who voted for it have to log in and
transfer their votes to other bugs to avoid "waisting" their votes. I propose
adding a category of "pending" votes - The pending vote would be counted as 0
votes, but as soon as some bug is resolved, its vote will be transfered to the
next pending vote (in the same category, of course).
Casting a "pending" vote can also be used to mark bugs that people consider
important, but do not have enough votes for. This way you can come in later, go
to the votes page and review your priorities, possibly replacing some pending
votes with real ones and vice versa.
Even better alternative would be to change the casting of votes from absolute
(e.g. I give some specific number of votes for each bug) to relative. In this
scheme, users would be able to assing to each bug an arbitrary "weight". At each
point in time, each person's vote allotment for each section would be divided
among all _unresolved_ bugs proportional to the assigned weights.
For example, if I have 5 votes and I assign
bug 1 - weight 7
bug 2 - weight 3
bug 3 - weight 3
and then bug 3 would get resolved, my votes will get automatically redistributed
as 3.5 for bug 1 and 1.5 for bug 2.
I believe this is a reasonable alternative to "whining about votes on resolved
bugs - see bug #27553
Comment 1•24 years ago
|
||
I sometmies deliberately vote for bugs that are marked "invalid" or "wontfix",
and I wouldn't want my votes shifted to other bugs automatically.
Comment 2•24 years ago
|
||
Also what to do if someone resolves and then it gets reopened. If your vote
disappears you won't be notified of the reopening either.
OS: Linux → All
Hardware: PC → All
Target Milestone: --- → Future
Comment 3•23 years ago
|
||
Solution to Jesse's concern: a pref to either shift votes for all resolved bugs,
only shift votes for fixed bugs - or never shift votes.
Solution to Matthew's concern: pref to turn ordinary votes back into pending
votes for resolved/fixed/no bugs. Pending votes could still keep you on the
email list.
Robin, might want to also include option to transfer when bug is closed. I've
had to re-vote for one that was resolved fixed, then reopened. Now I wait for
them to close to move votes...
See also bug 92440 (Upstream Voting)
Comment 5•23 years ago
|
||
-> Bugzilla product
Assignee: tara → myk
Component: Bugzilla → Creating/Changing Bugs
Product: Webtools → Bugzilla
Version: other → unspecified
Comment 6•21 years ago
|
||
It would be good to have pending votes, but no automatic moving.
If I wanted to vote for 13 bugs, I could then chose 10 of them and let the rest
as pending, and chose another of the pending bugs when one of the 10 was fixed.
IOW, the pending bugs list would be more of a reminder that I once wanted to
vote for the bugs but didn't because I did not have enought votes.
I use a Saved Search called "Wishlist" to hold bugs i can't vote for yet.
I suggest closing this bug in favor of bug 92440.
Comment 8•18 years ago
|
||
AFAIU bug 92440 is a different solution to a different problem.
This one deals with "what happens when a bug I've voted for gets resolved".
Bug 92440 deals with "what happens if a bug I'm voting for needs something else to get resolved first?".
Assuming I've understood things correctly, closing one in favour of the other doesn't make sense.
Updated•18 years ago
|
QA Contact: mattyt-bugzilla → default-qa
Updated•18 years ago
|
Target Milestone: Future → ---
Updated•18 years ago
|
Assignee: myk → create-and-change
Updated•18 years ago
|
Priority: -- → P5
Comment 9•17 years ago
|
||
We are not going to implement a user pref for this ("should we remove votes on resolved bugs?") nor alter the DB schema for such a minor benefit. If the vote limit is a problem, ask the admin to increase it. But this RFE doesn't worth the code complexity.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•