From d8caf6045d10344c431918128e3803ca497565f3 Mon Sep 17 00:00:00 2001 From: "gerv%gerv.net" <> Date: Sun, 28 Jul 2002 05:00:17 +0000 Subject: Merging new docs from 2.16 branch. --- docs/html/voting.html | 195 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 195 insertions(+) create mode 100644 docs/html/voting.html (limited to 'docs/html/voting.html') diff --git a/docs/html/voting.html b/docs/html/voting.html new file mode 100644 index 000000000..47b05647f --- /dev/null +++ b/docs/html/voting.html @@ -0,0 +1,195 @@ +Voting
The Bugzilla Guide
PrevChapter 5. Administering BugzillaNext

5.4. Voting

Voting allows users to be given a pot of votes which they can allocate + to bugs, to indicate that they'd like them fixed. + This allows developers to gauge + user need for a particular enhancement or bugfix. By allowing bugs with + a certain number of votes to automatically move from "UNCONFIRMED" to + "NEW", users of the bug system can help high-priority bugs garner + attention so they don't sit for a long time awaiting triage.

To modify Voting settings:

  1. Navigate to the "Edit product" screen for the Product you + wish to modify

  2. Maximum Votes per person: + Setting this field to "0" disables voting.

  3. Maximum Votes a person can put on a single + bug": + It should probably be some number lower than the + "Maximum votes per person". Don't set this field to "0" if + "Maximum votes per person" is non-zero; that doesn't make + any sense.

  4. Number of votes a bug in this product needs to + automatically get out of the UNCONFIRMED state: + Setting this field to "0" disables the automatic move of + bugs from UNCONFIRMED to NEW. +

  5. Once you have adjusted the values to your preference, click + "Update".

PrevHomeNext
Product, Component, Milestone, and Version AdministrationUpGroups and Group Security
\ No newline at end of file -- cgit v1.2.3-24-g4f1b