Closed Bug 232914 Opened 22 years ago Closed 18 years ago

time tracking with dependencies

Categories

(Bugzilla :: Bugzilla-General, enhancement)

x86
All
enhancement
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 286452

People

(Reporter: john, Unassigned)

Details

User-Agent: Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031225 Firebird/0.7 There should be an easy way to get cumulative time tracking info for a bug and its dependencies. Currently, one must: 1. follow "Show dependency tree" link of bug in question 2. follow "view as bug list" link for dependency output 3. if necessary, follow "Change colums" link and add "Orig. Est.", "Hours Left", and "actual_time" fields 4. follow "CSV" link and save as file 5. import file into spreadsheet and sum the time fields Instead, cumulative time information should be included for each node in the "show dependency tree" output. If this task is resource-intensive, a separate link could be provided on the bug page, such as "show time dependency tree". Ideally, the cumulative info would include the same items currently on the bug page (Orig. Est., Current Est., Hours Worked, %Complete). In addition, in the thee output, it would be helpful to visually mark bugs that do not have time information. Reproducible: Didn't try Steps to Reproduce: 1. 2. 3.
It would be nice too if it can be summarize original/current estimated and hours left in tabular reports. For example: I like to see how many hours need to each developer to work to solve bugs for a specified target milestone.
Reassigning bugs that I'm not actively working on to the default component owner in order to try to make some sanity out of my personal buglist. This doesn't mean the bug isn't being dealt with, just that I'm not the one doing it. If you are dealing with this bug, please assign it to yourself.
Assignee: justdave → general
QA Contact: mattyt-bugzilla → default-qa
I think that this works now in 2.21.1...
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.