The current documentation says: "Don't worry about the "Closed for bug entry", "Maximum Votes per person", "Maximum votes a person can put on a single bug", "Number of votes a bug in this Product needs to automatically get out of the UNCONFIRMED state", and "Version" options yet. We'll cover those in a few moments." Wow, so useful!
I'm adding a bunch of stuff to this section in bug 397665. The patch in there is still under review. That bit has not been taken out in my patch (yet). I assumed when reading that bit that indeed we did cover those "in a few moments", but i'm now thinking they never do get covered. So, when the other bug get's approved I'd like to take out this paragraph and add documentation for these items.
Assignee: documentation → sam.folkwilliams
Created attachment 298038 [details] [diff] [review] draft 1 added a description of all the product fields. also added xref's to some sections for more detail (needed also to add "xreflabel" bits to other sections). Also found some existing spelling errors.
Attachment #298038 - Flags: review?(documentation)
Comment on attachment 298038 [details] [diff] [review] draft 1 > <glossterm linkend="gloss-product" baseform="product"> >- Products</glossterm> Unrelated to this patch: did you note that this link doesn't work? The glossary has no anchor for "product". r=LpSolit
Attachment #298038 - Flags: review?(documentation) → review+
Colin, reopen if you want to see this doc patch in 2.20 and 2.22 too (it doesn't apply cleanly and would need to be backported). tip: Checking in docs/xml/administration.xml; /cvsroot/mozilla/webtools/bugzilla/docs/xml/administration.xml,v <-- administration.xml new revision: 1.81; previous revision: 1.80 done 3.0.3: Checking in docs/xml/administration.xml; /cvsroot/mozilla/webtools/bugzilla/docs/xml/administration.xml,v <-- administration.xml new revision: 188.8.131.52; previous revision: 184.108.40.206 done
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
Target Milestone: Bugzilla 2.20 → Bugzilla 3.0
You need to log in before you can comment on or make changes to this bug.