51a7de4d46
The README is now gutted, pointers to Guide. Also some new sections added, old ones fixed, and notes appended to deprecated sections I've not yet had the heart to remove. git-svn-id: svn://10.0.0.236/trunk@93058 18797224-902f-48f8-a5cc-f745e15eee43
197 lines
6.1 KiB
HTML
197 lines
6.1 KiB
HTML
<HTML
|
|
><HEAD
|
|
><TITLE
|
|
>Better Searching</TITLE
|
|
><META
|
|
NAME="GENERATOR"
|
|
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
|
|
"><LINK
|
|
REL="HOME"
|
|
TITLE="The Bugzilla Guide"
|
|
HREF="index.html"><LINK
|
|
REL="UP"
|
|
TITLE="The Future of Bugzilla"
|
|
HREF="future.html"><LINK
|
|
REL="PREVIOUS"
|
|
TITLE="Reducing Spam"
|
|
HREF="spamlite.html"><LINK
|
|
REL="NEXT"
|
|
TITLE="Description Flags and Tracking Bugs"
|
|
HREF="trackingbugs.html"></HEAD
|
|
><BODY
|
|
CLASS="SECTION"
|
|
BGCOLOR="#FFFFFF"
|
|
TEXT="#000000"
|
|
LINK="#0000FF"
|
|
VLINK="#840084"
|
|
ALINK="#0000FF"
|
|
><DIV
|
|
CLASS="NAVHEADER"
|
|
><TABLE
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
CELLPADDING="0"
|
|
CELLSPACING="0"
|
|
><TR
|
|
><TH
|
|
COLSPAN="3"
|
|
ALIGN="center"
|
|
>The Bugzilla Guide</TH
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="left"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="spamlite.html"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="80%"
|
|
ALIGN="center"
|
|
VALIGN="bottom"
|
|
>Chapter 6. The Future of Bugzilla</TD
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="right"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="trackingbugs.html"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"></DIV
|
|
><DIV
|
|
CLASS="SECTION"
|
|
><H1
|
|
CLASS="SECTION"
|
|
><A
|
|
NAME="SEARCHING"
|
|
>6.2. Better Searching</A
|
|
></H1
|
|
><P
|
|
><P
|
|
CLASS="LITERALLAYOUT"
|
|
>Current searching tools in Bugzilla include the querying mechanism,<br>
|
|
special summary reports and dependency trees. This message is about new<br>
|
|
facilities.<br>
|
|
<br>
|
|
1. General Summary Reports<br>
|
|
<br>
|
|
For some time now it has been apparent to me that the query bug list<br>
|
|
leaves a little to be desired in its linear nature. There is a need to<br>
|
|
have categorised subsets, and counts of each category. If you don't<br>
|
|
believe me, how about these facilities already in place or which people<br>
|
|
have asked for:<br>
|
|
<br>
|
|
Most Doomed Reports - Categorised On Assignee, Shows and Counts Number<br>
|
|
of Bugs For Each Assignee<br>
|
|
Bug #15806 (Most Voted For Bugs) - Categorised On Product, Shows Bugs<br>
|
|
Voters Most Want Fixed<br>
|
|
Bug #9789 (BugAThon Tracking Page) - Categorised On Developer (Subset),<br>
|
|
Counts Number of Bugs<br>
|
|
Bug #9409 and #9411 - The desire to be able to report on more subsets.<br>
|
|
<br>
|
|
Hopefully you can see the gist of what is desired here. It's a general<br>
|
|
reporting mechanism.<br>
|
|
<br>
|
|
This mechanism lets you choose the subset of bugs to operate on (like<br>
|
|
query), let's you categorise them, possibly along with subcategories and<br>
|
|
counts the number of bugs within each category. It might or might not<br>
|
|
show the actual bugs themselves, and it might limit the number of bugs<br>
|
|
within a category, or categories to report on.<br>
|
|
<br>
|
|
I'm further sure that many applications of this mechanism would only be<br>
|
|
recognised once it was implemented.<br>
|
|
<br>
|
|
The general summary reports bug is at<br>
|
|
"http://bugzilla.mozilla.org/show_bug.cgi?id=12282".<br>
|
|
<br>
|
|
2. Related Bugs<br>
|
|
<br>
|
|
It would be nice to have a field where you could enter other bugs<br>
|
|
related to the current bug - it would be handy for navigation and<br>
|
|
possibly even finding duplicates. See<br>
|
|
"http://bugzilla.mozilla.org/show_bug.cgi?id=12286".<br>
|
|
<br>
|
|
3. Column Specification Support<br>
|
|
<br>
|
|
Currently query seems to get what columns to report on from whatever the<br>
|
|
user last used. This doesn't work well for "prepackaged queries", where<br>
|
|
you followed a link. You can probably add a column by specifying a sort<br>
|
|
column, but this is difficult and suboptimal.<br>
|
|
<br>
|
|
Furthermore, I find that when I want to add a column to a query, it's<br>
|
|
usually a one off and I would prefer it to go away for the next query. <br>
|
|
Hence, it would be nice to specify the columns that appear on the query<br>
|
|
(and general summary report) pages. The default query mechanism should<br>
|
|
be able to let you specify your default columns.<br>
|
|
<br>
|
|
This proposal lives at<br>
|
|
"http://bugzilla.mozilla.org/show_bug.cgi?id=12284".</P
|
|
></P
|
|
></DIV
|
|
><DIV
|
|
CLASS="NAVFOOTER"
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"><TABLE
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
CELLPADDING="0"
|
|
CELLSPACING="0"
|
|
><TR
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="left"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="spamlite.html"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="34%"
|
|
ALIGN="center"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="index.html"
|
|
>Home</A
|
|
></TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="trackingbugs.html"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="left"
|
|
VALIGN="top"
|
|
>Reducing Spam</TD
|
|
><TD
|
|
WIDTH="34%"
|
|
ALIGN="center"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="future.html"
|
|
>Up</A
|
|
></TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
>Description Flags and Tracking Bugs</TD
|
|
></TR
|
|
></TABLE
|
|
></DIV
|
|
></BODY
|
|
></HTML
|
|
> |