summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorlpsolit%gmail.com <>2008-01-20 04:55:44 +0100
committerlpsolit%gmail.com <>2008-01-20 04:55:44 +0100
commitf4c6a69d5113b8edfc1e59640ef5de66b297522b (patch)
tree6aa8a67d4f27afce65b57fa586db597d284c86c6
parent853dfe716c34c6d605513d885c932359884f5e9c (diff)
downloadbugzilla-f4c6a69d5113b8edfc1e59640ef5de66b297522b.tar.gz
bugzilla-f4c6a69d5113b8edfc1e59640ef5de66b297522b.tar.xz
Bug 403397: Missing documentation about keywords - Patch by Sam Folk-Williams <sam.folkwilliams@gmail.com> r=Colin
-rw-r--r--docs/xml/administration.xml24
1 files changed, 24 insertions, 0 deletions
diff --git a/docs/xml/administration.xml b/docs/xml/administration.xml
index 83f88630e..5ece531a5 100644
--- a/docs/xml/administration.xml
+++ b/docs/xml/administration.xml
@@ -1396,6 +1396,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 admin page. 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>