Open Bug 120687 Opened 24 years ago Updated 16 years ago

show bug list as dependency graph

Categories

(Bugzilla :: Dependency Views, enhancement, P3)

2.15
enhancement

Tracking

()

People

(Reporter: jayvdb, Unassigned)

References

Details

Attachments

(3 files)

The best example of how this is useful is a 'Release Blockers' bug list. A list or a tree of these is not the best way of finding which bugs need to be chased up first. The graph also shows area's which are going to put most stress on the tree, and thus might be better to lock the tree or create a branch.
Attached patch v1Splinter Review
Depends on: 120686
So what happens if the bugs are not necessarily connected to each other? CCing myk, as he's templatising buglist.cgi. Gerv
This is our release blockers dependancy graph from a buglist: id=6,16,26,33,39,42,64,113,115,116,117,120,133,134,137,142,143,147,148,156 They are displayed on the left of the graph, and from what I can see graphviz is placing sets of bugs top to bottom ranked on number of edges.
Comment on attachment 65538 [details] [diff] [review] v1 >Index: buglist.cgi >=================================================================== >RCS file: /cvsroot/mozilla/webtools/bugzilla/buglist.cgi,v >retrieving revision 1.155 >diff -u -r1.155 buglist.cgi >--- buglist.cgi 2001/12/30 05:46:24 1.155 >+++ buglist.cgi 2002/01/18 01:48:56 >@@ -1737,6 +1740,9 @@ > print qq{&nbsp;&nbsp;\n}; > print qq{<NOBR><A HREF="query.cgi?$::buffer">Edit this query</A></NOBR>\n}; > >+ $buglist = join(",", @bugarray); >+ print qq{&nbsp;&nbsp;\n}; >+ print qq{<NOBR><A HREF="showdependencygraph.cgi?id=$buglist">Dependency Graph</A></NOBR>\n}; > print "</FORM>\n"; > } > Not a bad idea, and it looks like the issue of bugs being related to each other is taken care of in the screen-shot, where (correct me if I'm wrong) unrelated bugs are lined up vertically without any lines being drawn between them. This patch is missing an implementation, however, since the version of showdependencygraph.cgi in the CVS repository only accepts a single bug ID from which to build the graph. Are there patches for that CGI as well? If so, please attach a patch file with both patches included.
Attachment #65538 - Flags: review-
Myk, see bug 120686, which this bug is marked as depending on
Reassigning to zeroJ. Gerv
Assignee: gerv → zeroJ
Comment on attachment 65538 [details] [diff] [review] v1 Rescinding my "needs-work" status since the implementation I thought was missing exists in bug 120686.
Attachment #65538 - Flags: review-
Severity: normal → enhancement
Priority: -- → P3
Target Milestone: --- → Bugzilla 2.18
Comment on attachment 65538 [details] [diff] [review] v1 This has been templatised, + tags should be lowercased.
Attachment #65538 - Flags: review-
Summary: show bug list as dependancy graph → show bug list as dependency graph
Target Milestone: Bugzilla 2.18 → Bugzilla 2.20
Bugzilla 2.20 feature set is now frozen as of 15 Sept 2004. Anything flagged enhancement that hasn't already landed is being pushed out. If this bug is otherwise ready to land, we'll handle it on a case-by-case basis, please set the blocking2.20 flag to '?' if you think it qualifies.
Target Milestone: Bugzilla 2.20 → Bugzilla 2.22
Calling structured "graph" representation of buglist will be appropriate in links to alternative bug representations as: "Graph | CSV | iCalendar" To do so, just apply this small (3-lines) patch.
Assignee: jayvdb → gerv
QA Contact: mattyt-bugzilla → default-qa
Target Milestone: Bugzilla 2.22 → ---
Component: Reporting/Charting → Dependency Views
Assignee: gerv → dependency.views
bug 371030, bug 12992, bug 120687 seem to be dupes of each other.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: