summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorjocuri%softhome.net <>2008-04-04 13:47:52 +0200
committerjocuri%softhome.net <>2008-04-04 13:47:52 +0200
commit29f22cde1a39df57e55d7216e607a49de78b747e (patch)
tree3fd13199a1ac8419bc400030ac66f85e4467a622
parentae807c41d7b8ab69bd085839b731524e1a15656a (diff)
downloadbugzilla-29f22cde1a39df57e55d7216e607a49de78b747e.tar.gz
bugzilla-29f22cde1a39df57e55d7216e607a49de78b747e.tar.xz
Documentation patch for bug 328330: Add classifications documentation; patch by Vlad Dascalu <vladd@bugzilla.org>, r=kevin.benton@amd.com, r=LpSolit@gmail.com.
-rw-r--r--docs/en/xml/administration.xml21
1 files changed, 20 insertions, 1 deletions
diff --git a/docs/en/xml/administration.xml b/docs/en/xml/administration.xml
index c300cb36e..17ffacc44 100644
--- a/docs/en/xml/administration.xml
+++ b/docs/en/xml/administration.xml
@@ -576,6 +576,25 @@
</section>
</section>
+ <section id="classifications">
+ <title>Classifications</title>
+
+ <para>Classifications tend to be used in order to group several related
+ products into one distinct entity.</para>
+
+ <para>The classifications layer is disabled by default; it can be turned
+ on or off using the useclassification parameter,
+ in the <emphasis>Bug Fields</emphasis> section of the edit parameters screen.</para>
+
+ <para>Access to the administration of classifications is controlled using
+ the <emphasis>editclassifications</emphasis> system group, which defines
+ a privilege for creating, destroying, and editing classifications.</para>
+
+ <para>When activated, classifications will introduce an additional
+ step when filling bugs (dedicated to classification selection), and they
+ will also appear in the advanced search form.</para>
+ </section>
+
<section id="products">
<title>Products</title>
@@ -583,7 +602,7 @@
<glossterm linkend="gloss-product" baseform="product">
Products</glossterm>
- are the broadest category in Bugzilla, and tend to represent real-world
+ tend to represent real-world
shipping products. E.g. if your company makes computer games,
you should have one product per game, perhaps a "Common" product for
units of technology used in multiple games, and maybe a few special