From: lpsolit%gmail.com <>
Date: Mon, 12 Feb 2007 04:23:43 +0000 (+0000)
Subject: Doc patch for bug 250410 (implement the Time Summary feature) and bug 283139 (setting... 
X-Git-Tag: bugzilla-2.22.3~21
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=e84db18daa0fb77edd6bcf538c5891b29ca399b6;p=thirdparty%2Fbugzilla.git

Doc patch for bug 250410 (implement the Time Summary feature) and bug 283139 (setting the remaining time to zero when resolving a bug) - Patch by Frédéric Buclin <LpSolit@gmail.com> r=justdave
---

diff --git a/docs/xml/using.xml b/docs/xml/using.xml
index a9cf3ba272..635b1eb875 100644
--- a/docs/xml/using.xml
+++ b/docs/xml/using.xml
@@ -948,6 +948,34 @@
     </section>
   </section>
 
+  <section id="timetracking">
+    <title>Time Tracking Information</title>
+
+    <para>
+      Users who belong to the group specified by the <quote>timetrackinggroup</quote>
+      parameter have access to time-related fields. Developers can see
+      deadlines and estimated times to fix bugs, and can provide time spent
+      on these bugs.
+    </para>
+
+    <para>
+      At any time, a summary of the time spent by developers on bugs is
+      accessible either from bug lists when clicking the <quote>Time Summary</quote>
+      button or from individual bugs when clicking the <quote>Summarize time</quote>
+      link in the time tracking table. The <filename>summarize_time.cgi</filename>
+      page lets you view this information either per developer or per bug,
+      and can be split on a month basis to have greater details on how time
+      is spent by developers.
+    </para>
+
+    <para>
+      As soon as a bug is marked as RESOLVED, the remaining time expected
+      to fix the bug is set to zero. This lets QA people set it again for
+      their own usage, and it will be set to zero again when the bug will
+      be marked as CLOSED.
+    </para>
+  </section>
+
   <section id="userpreferences">
     <title>User Preferences</title>