Closed
Bug 69793
Opened 24 years ago
Closed 24 years ago
check in new files for QuickSearch
Categories
(Bugzilla :: Bugzilla-General, enhancement)
Bugzilla
Bugzilla-General
Tracking
()
VERIFIED
FIXED
Bugzilla 2.12
People
(Reporter: afranke, Assigned: Chris.Yeh)
References
()
Details
Attachments
(14 files)
|
2.17 KB,
text/plain
|
Details | |
|
19.07 KB,
text/plain
|
Details | |
|
4.61 KB,
text/html
|
Details | |
|
8.01 KB,
text/html
|
Details | |
|
878 bytes,
patch
|
Details | Diff | Splinter Review | |
|
1.13 KB,
patch
|
Details | Diff | Splinter Review | |
|
2.85 KB,
text/html
|
Details | |
|
308 bytes,
patch
|
Details | Diff | Splinter Review | |
|
22.95 KB,
patch
|
Details | Diff | Splinter Review | |
|
22.95 KB,
patch
|
Details | Diff | Splinter Review | |
|
395 bytes,
patch
|
Details | Diff | Splinter Review | |
|
552 bytes,
patch
|
Details | Diff | Splinter Review | |
|
473 bytes,
patch
|
Details | Diff | Splinter Review | |
|
1.29 KB,
patch
|
Details | Diff | Splinter Review |
This bug is a request to add the QuickSearch tool to the bugzilla cvs
repository. It is complementary to bug 61561 which is a request to integrate
this tool into the bugzilla front page on bugzilla.mozilla.org .
Description of the tool:
========================
The QuickSearch tool is an alternative query tool for bugzilla. The UI is as
simple as possible: a single text box. And it should be simple to use for
newbies: you can just enter some words and press return, and it will give you a
list of bugs.
Currently, this is a JS-based client-side tool, but it could be ported to perl
in the future.
Reasons for including it into CVS:
==================================
The tool can be useful for all bugzilla installations. All mozilla-specific
values are defined in a separate file (currently called "localconfig.js"), so it
should be easy to use it in other installations. It works fine for me so far,
and I already prefer it over query.cgi more than 80 percent of the time. I
consider it production level quality. Checking it in will hopefully increase the
chance that someone finds it useful and starts hacking on it.
Files involved:
===============
quicksearch.html (query form with first part of the documentation)
quicksearchhack.html (extended query form with second part of the documentation)
quicksearch.js (main part of the JS sources)
localconfig.js (installation-specific values)
optional: index.html (for integration into the front page)
I'm going to attach the files soon.
| Reporter | ||
Comment 1•24 years ago
|
||
| Reporter | ||
Comment 2•24 years ago
|
||
| Reporter | ||
Comment 3•24 years ago
|
||
| Reporter | ||
Comment 4•24 years ago
|
||
| Reporter | ||
Comment 5•24 years ago
|
||
| Reporter | ||
Comment 6•24 years ago
|
||
| Reporter | ||
Comment 7•24 years ago
|
||
| Reporter | ||
Comment 8•24 years ago
|
||
Ok, patches complete. Decorating bug with keywords and status whiteboard stuff.
Please review, approve, checkin asap. ;)
| Reporter | ||
Comment 9•24 years ago
|
||
Ok, maybe it was a little too much... :)
Whiteboard: 2.12, 2.14, 2.16, 2.18, 2.20, 3.0, 3.2, 3.4 or Future... → 2.12 ?
| Reporter | ||
Comment 10•24 years ago
|
||
| Reporter | ||
Comment 11•24 years ago
|
||
| Reporter | ||
Comment 12•24 years ago
|
||
| Reporter | ||
Comment 13•24 years ago
|
||
So I'm sorry that the first version was the wrong one. Attachment 26162 [details] [diff] from
02/25/01 4:12 is the correct one. The difference is that the new one only
searches for OPEN bugs:
319c319
< add("DUPLICATE",resolution);
---
> // add("DUPLICATE",resolution);
Having localconfig.js and quicksearch.js in the bugzilla cvs would have the
advantage that one could truly operate with diffs instead of whole files...
| Assignee | ||
Comment 15•24 years ago
|
||
I've applied all your patches (quicksearch.html, quicksearchhack.html,
index.html, localconfig.js and quicksearch.js) and the searching part of it
doesn't appear to work at all.
I have a bug with a summary of "google foo bar".
If I do a quick search for any of these summary words, I get zero bugs returned
from the query.
| Reporter | ||
Comment 16•24 years ago
|
||
It would probably help if I had the following info:
- the url of your bugzilla test installation
- the url generated by your query
- the browser name and version
| Assignee | ||
Comment 17•24 years ago
|
||
The bugzilla test installation is behind a firewall, so you will not be able to
reach it.
Communicator 4.7
http://crucible.bluemartini.com/mozilla/webtools/bugzilla/buglist.cgi?bug_status
=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&field0-0-0=p
roduct&type0-0-0=substring&value0-0-0=foo&field0-0-1=component&type0-0-1=substri
ng&value0-0-1=foo&field0-0-2=short_desc&type0-0-2=substring&value0-0-2=foo&field
0-0-3=status_whiteboard&type0-0-3=substring&value0-0-3=foo
| Reporter | ||
Comment 18•24 years ago
|
||
This is strange. I'm using Communicator 4.61, and the url is exactly what it
should be. If I replace the bugzilla location part
"http://crucible.bluemartini.com/mozilla/webtools/bugzilla/" with
"http://bugzilla.mozilla.org/", it works correctly.
Are you sure you have an _OPEN_ bug with foo in the summary? Can you find it
using your query.cgi form (select UNCONFIRMED,NEW,ASSIGNED,REOPENED, enter foo
in the summary field, and submit)?
Comment 19•24 years ago
|
||
moving to real milestones...
Whiteboard: 2.12 ?
Target Milestone: --- → Bugzilla 2.12
| Reporter | ||
Comment 20•24 years ago
|
||
| Reporter | ||
Comment 21•24 years ago
|
||
| Reporter | ||
Comment 22•24 years ago
|
||
| Reporter | ||
Comment 23•24 years ago
|
||
| Assignee | ||
Comment 24•24 years ago
|
||
new feature and patches checked into trunk
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 25•24 years ago
|
||
Verified fixed. All files have been checked in. Any bugs related to this feature
should be filed separately.
Comment 27•24 years ago
|
||
Moving closed bugs to Bugzilla product
Component: Bugzilla → Bugzilla-General
Product: Webtools → Bugzilla
Version: other → unspecified
Comment 28•23 years ago
|
||
*** Bug 33067 has been marked as a duplicate of this bug. ***
Updated•12 years ago
|
QA Contact: matty_is_a_geek → default-qa
You need to log in
before you can comment on or make changes to this bug.
Description
•