Closed Bug 154321 Opened 23 years ago Closed 23 years ago

Bugzilla voting functions don't appear on non-Browser Products

Categories

(bugzilla.mozilla.org :: General, defect)

PowerPC
macOS
defect
Not set
major

Tracking

()

VERIFIED INVALID

People

(Reporter: bugmail, Assigned: endico)

Details

Voting functions appear to be missing from bugs filed on such non-Browser Products such as Chimera and mozilla.org.
Blocks: 150783
Summary: Voting doesn't appear on non-Browser Products → Bugzilla voting functions don't appear on non-Browser Products
Voting functions only appear for products for which they have been enabled, which is not the case for the Chimera and mozilla.org components.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
No longer blocks: 150783
Myk, I'm fairly certain voting was enabled for Chimera prior to the upgrade. What's the procedure to either a) determine whether or not it was, or b) get it enabled?
Figuring out if it was or not requires me to do some painful database detective work. Getting it enabled is much easier. It just requires filing a bug in the "mozilla.org" product, "Bugzilla: other moz.org issues" requesting the change. Include your requested values for the following configuration parameters: Votes per user Max Votes per bug Votes to confirm
Myk, if I do that, will any votes people had previously cast be preserved, or is that data that will need to be retrieved from some old data store? I'm pretty certain people had used the function to cast votes on Chimera bugs.
Ok, I've done the detective work. Voting wasn't enabled for Chimera bugs before the upgrade, and there are no votes in the database for Chimera bugs.
Thanks, Myk. Sorry for the false alarm.
Maybe Chimera used to be a component in a voting product? I know that's been done way too much in the past, and would explain the confusion.
FYI, enablement request filed as bug 156839.
Status: RESOLVED → VERIFIED
Component: Bugzilla: Other b.m.o Issues → General
Product: mozilla.org → bugzilla.mozilla.org
You need to log in before you can comment on or make changes to this bug.