From: lpsolit%gmail.com <>
Date: Sun, 20 Jan 2008 03:57:53 +0000 (+0000)
Subject: Bug 403397: Missing documentation about keywords - Patch by Sam Folk-Williams <sam... 
X-Git-Tag: bugzilla-3.0.4~64
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=d5fbd9c6f25bc968c48cbd732dfe678f07b2f2d2;p=thirdparty%2Fbugzilla.git

Bug 403397: Missing documentation about keywords - Patch by Sam Folk-Williams <sam.folkwilliams@gmail.com> r=Colin
---

diff --git a/docs/xml/administration.xml b/docs/xml/administration.xml
index 75f54c34fd..7d42a264d1 100644
--- a/docs/xml/administration.xml
+++ b/docs/xml/administration.xml
@@ -1395,6 +1395,30 @@ foo: ENTRY, MANDATORY/MANDATORY, CANEDIT
 
   </section> <!-- flags -->
 
+  <section id="keywords">
+    <title>Keywords</title>
+
+    <para>
+    The administrator can define keywords which can be used to tag and
+    categorise bugs. For example, the keyword "regression" is commonly used.
+    A company might have a policy stating all regressions
+    must be fixed by the next release - this keyword can make tracking those
+    bugs much easier.
+    </para>
+    <para>
+    Keywords are global, rather than per-product. If the administrator changes
+    a keyword currently applied to any bugs, the keyword cache must be rebuilt
+    using the <xref linkend="sanitycheck"/> script. Currently keywords can not
+    be marked obsolete to prevent future usage.
+    </para>
+    <para>
+    Keywords can be created, edited or deleted by clicking the "Keywords"
+    link in the footer. There are two fields for each keyword - the keyword
+    itself and a brief description. Once created, keywords can be selected
+    and applied to individual bugs in that bug's "Details" section.
+    </para>
+  </section>
+
   <section id="custom-fields">
     <title>Custom Fields</title>