From bacdf9b28a1bd399ee7c8aa3a38eb9aa52915ac5 Mon Sep 17 00:00:00 2001 From: "lpsolit%gmail.com" <> Date: Fri, 4 Apr 2008 11:48:08 +0000 Subject: 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 r=justdave 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(+) (limited to 'docs/en') 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 @@ +
+ Time Tracking Information + + + Users who belong to the group specified by the timetrackinggroup + 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. + + + + At any time, a summary of the time spent by developers on bugs is + accessible either from bug lists when clicking the Time Summary + button or from individual bugs when clicking the Summarize time + link in the time tracking table. The summarize_time.cgi + 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. + + + + 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. + +
+
User Preferences -- cgit v1.2.3-24-g4f1b