From bacdf9b28a1bd399ee7c8aa3a38eb9aa52915ac5 Mon Sep 17 00:00:00 2001
From: "lpsolit%gmail.com" <>
Date: Fri, 4 Apr 2008 11:48:08 +0000
Subject: [PATCH] =?UTF-8?q?Doc=20patch=20for=20bug=20250410=20(implement?=
=?UTF-8?q?=20the=20Time=20Summary=20feature)=20and=20bug=20283139=20(sett?=
=?UTF-8?q?ing=20the=20remaining=20time=20to=20zero=20when=20resolving=20a?=
=?UTF-8?q?=20bug)=20-=20Patch=20by=20Fr=C3=83=C2=A9d=C3=83=C2=A9ric=20Buc?=
=?UTF-8?q?lin=20<LpSolit@gmail.com>=20r=3Djustdave?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
---
docs/en/xml/using.xml | 28 ++++++++++++++++++++++++++++
1 file changed, 28 insertions(+)
diff --git a/docs/en/xml/using.xml b/docs/en/xml/using.xml
index 16f951f4f..0d49e2ae2 100644
--- a/docs/en/xml/using.xml
+++ b/docs/en/xml/using.xml
@@ -1021,6 +1021,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>
--
2.24.1