220995 - product/component-specific query links generator

Status: RESOLVED WONTFIX

(Bugzilla :: User Interface, enhancement)

Description

[Ludovic Dubost]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20030925
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20030925

This patch allows to browse bugs by product and components..
Once you have chosen your product, it will display links to access for each
component:

- All bugs
- All open bugs
- All bugs assigned to the currently logged user
- All bugs reported by the currently logged user


Reproducible: Always

Steps to Reproduce:

Comment 1

[Ludovic Dubost]

Attachment: Patch against 2.17 Head

This is the patch for the above specified feature.. This patch adds 2 files and
patches index.html.tmpl and usefull-links.html.tmpl. It should work on most
versions of bugzilla.

Comment 2

[Dave Miller [:justdave]]

see also bug 194272.  (is it a dupe?)

Comment 3

[Vlad Dascalu]

Ludovic: if you plan to integrate your contributed patches into CVS, then please
set the r? flag, otherwise you could mention why CVS integration is not
suitable. Thanks! :-)

Comment 4

[Ludovic Dubost]

I would be to happy that somebody check it in CVS or do it myself.. However I
don't know the procedure for this.. Is there any documentation about the
procedure to follow for this except setting the 'r' flag ?

Ludovic

Comment 5

[Vlad Dascalu]

In order to get a patch checked in, here are the general steps:

1) attach a patch to a bug.
2) click "edit" next to the patch and put a "?" next to the review flag (this
will tell the Bugzilla reviewers that you want to integrate your patch into CVS).
3) wait for the "r+" flag; if you get a denied review ("r-"), improve your
patch, upload the new version and go back to step 1.
4) once you get the "r+" flag, put a "?" next to the approval flag.
5) wait for the approval (made by justdave or one of his assignees, mostly
module owners regarding their suitable expertise areas, like gerv for charts,
jake for documentation or myk for UI)
6) once you got that, your patch will be checked into CVS pretty fast, otherwise
feel free to bug a CVS commiter on IRC or on the mailing list.

You can find the community reviewers at http://bugzilla.org/who_we_are.html (at
the bottom, right after the module owners). Feel free to target some specific
reviewers during step 2 by specifically filling their email address next to the
"?" flag. Targeting specific reviewers is generally made using 2 criterias:

-> the expertise of the reviewer (those are listed at
http://bugzilla.org/who_we_are.html ).
-> the current workload of the reviewer reported to its current level of
activity and involment (you can use http://bugzilla.mozilla.org/request.cgi to
query pending requests againest the Bugzilla product).

Additional information can be found at http://bugzilla.org/developerguide.html ,
for example in the section "Submitting Your Patch".

Comment 6

[chaduv]

You've got a few lines like: <td valign=top><a href="[% baseurl %][% bug_status 
%][% assignedto %]">My Assigned bugs</a></td> -- need to consistently use 
terms.bugs in the patch, rather than just hit or miss.

You might want to request review from a specific person, or ask in irc if 
someone is willing.

Comment 7

[Myk Melez [:myk] [@mykmelez]]

I'm having a hard time seeing the general usefulness of this patch for Bugzilla
installations.  The links it provides are easy to construct using the query
form, and it's hard to imagine many Bugzilla users wanting so many of them that
it's worth precreating them.

Also, when I think of "browsing by product or component" I imagine a
hierarchical list of products, components, and bugs that I can browse like a
file browser, perhaps with filters for limiting bugs based on reporter,
assignee, etc.  This doesn't remind me very much of other interfaces for browsing.

I'm inclined to say that this makes more sense as a Bugzilla extension than a
part of the main Bugzilla codebase.  It can take advantage of the new hooks
mechanism (http://www.bugzilla.org/docs/html/cust-hooks.html) to insert its link
into the home page.  I suggest something other than "browse" for the name,
though, perhaps "querymaker" or some such.