Closed Bug 16027 Opened 21 years ago Closed 17 years ago

Don't allow voting on resolved bugs.

Categories

(Bugzilla :: Creating/Changing Bugs, enhancement)

enhancement
Not set

Tracking

()

RESOLVED WONTFIX

People

(Reporter: CodeMachine, Assigned: myk)

Details

What to do with resolved bugs and voting?

I suggest it's OK as it is with resolved bugs keeping their votes.  After all,
they can be reopened.

I suggest the votes should be nuked once they are "closed" though, if that
doesn't already occur (its note like many bugs are actually closed yet).

Oh, and that you shouldn't be able to change your vote for a resolved/verified
bug other than to 0.  Currently you can vote for one.
I'm mostly worried about bugs getting reopened.  If a bug is closed, and then
reopened, it would be nice if the votes didn't evaporate.

People will get mail when the bug they have voted on gets closed.  I hope
they're paying attention to then move their votes...

Either way, this is all less than ideal.
Agree, that's why my proposals are conservative.  The JDC basically works the
same way as bugzilla now.
Status: NEW → ASSIGNED
Bug #27553 is a newer proposal.
tara@tequilarista.org is the new owner of Bugzilla and Bonsai.  (For details,
see my posting in netscape.public.mozilla.webtools,
news://news.mozilla.org/38F5D90D.F40E8C1A%40geocast.com .)
Assignee: terry → tara
Status: ASSIGNED → NEW
... which even if implemented, would leave this as a proposal to not be able to
change your number of votes on RESOLVED bugs to anything but 0.
Adding default QA contact to all open Webtools/Bugzilla bugs lacking one.
Sorry for the spam.
QA Contact: matty
Target Milestone: --- → Future
Moving to new Bugzilla product ...
Assignee: tara → myk
Component: Bugzilla → Creating/Changing Bugs
Product: Webtools → Bugzilla
Version: other → unspecified
Severity: enhancement → minor
Summary: Handle resolved bugs and voting → Don't allow voting on resolved bugs.
Target Milestone: Future → Bugzilla 2.16
We are currently trying to wrap up Bugzilla 2.16.  We are now close enough to
release time that anything that wasn't already ranked at P1 isn't going to make
the cut.  Thus this is being retargetted at 2.18.  If you strongly disagree with
this retargetting, please comment, however, be aware that we only have about 2
weeks left to review and test anything at this point, and we intend to devote
this time to the remaining bugs that were designated as release blockers.
Target Milestone: Bugzilla 2.16 → Bugzilla 2.18
This should not be fixed.  I'm currently voting for 5 "invalid" bugs, and I'm 
not the only person who intentionally votes for bugs marked as invalid.  I'd 
rather not have to spam those bugs with "me too"s -- isn't that one of the 
major advantages of having the voting feature?
Severity: minor → enhancement
Following the logic in bug 27553 by gerv, this is a WONTFIX. If it's a bug, and 
voting is enabled, you can vote on it. When you attempt to vote on another bug, 
the voting page shows non-open bugs with a strikethrough, so it's obvious which 
are closed and which aren't.

Empower the bugreporter! Let them choose where they put their votes!
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WONTFIX
Priority: P3 → --
Target Milestone: Bugzilla 2.18 → ---
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.