Closed Bug 12992 Opened 25 years ago Closed 14 years ago

Dependency Tree Views Of Bug Lists

Categories

(Bugzilla :: Creating/Changing Bugs, enhancement, P3)

Product:
Bugzilla
Component:
Creating/Changing Bugs
Type:
enhancement

Tracking

()

Status:
RESOLVED DUPLICATE of bug 371030

People

(Reporter: CodeMachine, Unassigned)

References

Details

(Whiteboard: [relations:depend]) 

I've seen the dependency tree view.  It would be nice if you could get a tree
view of a bug list, like you get back from a query or summary (bug #12282).
This tree view would work like the dependency tree, except every bug in the list
would be a root, unlike the dependency tree which has one.

This could help eliminate "tracking bugs", since you could use bug flags (bug
#11155), and get the dependency tree for all the bugs with that flag.
Status: NEW → ASSIGNED
tara@tequilarista.org is the new owner of Bugzilla and Bonsai.  (For details,
see my posting in netscape.public.mozilla.webtools,
news://news.mozilla.org/38F5D90D.F40E8C1A%40geocast.com .)
Assignee: terry → tara
Status: ASSIGNED → NEW
Assignee: tara → donm
Don--more graphics stuff
Status: NEW → ASSIGNED
3.0:  We need to do this to get rid of bad tracking bugs.
Whiteboard: 3.0
Whiteboard: 3.0 → 3.2
Adding default QA contact to all open Webtools/Bugzilla bugs lacking one.
Sorry for the spam.
QA Contact: matty
moving to real milestones...
Whiteboard: 3.2
Target Milestone: --- → Bugzilla 3.2
to the bz3 component
Component: Bugzilla → Bugzilla 3
Blocks: 86547
The Bugzilla 3 component is going away.  We're going to depend on the Milestones 
for this.  At the time this component was created, we didn't have milestones for 
Bugzilla.
Component: Bugzilla 3 → Bugzilla
Component: Bugzilla → Creating/Changing Bugs
Product: Webtools → Bugzilla
Version: other → unspecified
Reassigning to default owner.
Whiteboard: [relations:depend]
.
Assignee: donm → myk
Status: ASSIGNED → NEW
Voting for this enhancement - I am using Bugzilla for scheduling, and would find 
this feature extremely useful for creating a prioritized hierarchical list of 
development tasks.

The next best thing would be the ability to add a dependencies column containing 
comma-separated lists of hyperlinked bug numbers.

It could have a real interest to display 2 new columns in the list view :

- 1 corresponding to the number of bugs from the "Bug # depends on"
- 1 corresponding to the number of bugs from the "Bug # blocks"

As for other columns, the display of these 2 new columns should be disabled
using the "Change Columns" link.
I filed my column suggestion from comment #10 as a new bug #202292.

Note that this is really easy to do -- just change the showdependencytree.cgi
API a bit and change the data structure to allow for supplying data for a list
of bugs instead of a single bug.
QA Contact: mattyt-bugzilla → default-qa
Viewing query results as dependency trees would be a really useful feature. Here's my vote for it.
Assignee: myk → create-and-change
this could help in triaging. so if you have search results that return bugs A, B, C, D, E, you might have a graph like

  A

  C <- B <- Z 
  |    |
  E    D
  
And the graph should highlight A, B, C, D, E in the graph
Bugzilla 3.2 is now frozen. Only enhancements blocking 3.2 or specifically approved for 3.2 may be checked in to the 3.2 branch. If you would like to nominate your enhancement for Bugzilla 3.2, set the "blocking3.2" flag to "?". Then, either the target milestone will be changed back, or the blocking3.2 flag will be granted, if we will accept this enhancement for Bugzilla 3.2.

This particular bug has not been touched in over eight months, and thus is being retargeted to "---" instead of "Bugzilla 4.0". If you believe this is a mistake, feel free to retarget it to Bugzilla 4.0.
Target Milestone: Bugzilla 3.2 → ---
somehow related to bug 371030 .
bug 371030, bug 12992, bug 120687 seem to be dupes of each other.
Duping to bug 371030, which is in a much more advanced state, and already has many useful inputs (and even some great screenshots!).

Bug 120687 is not a dupe as it's about dependency graphs, not dependency trees. But they are related for sure.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.