From f4966aeb0e7a655c986aeb285c1a220274ddbfd9 Mon Sep 17 00:00:00 2001 From: "lpsolit%gmail.com" <> Date: Mon, 22 Aug 2005 01:16:40 +0000 Subject: Bug 70907: QuickSearch: port the JS code to perl (make it server-side) - Patch by Marc Schumann r=wicked a=myk --- quicksearch.html | 151 ------------------------------------------------------- 1 file changed, 151 deletions(-) delete mode 100644 quicksearch.html (limited to 'quicksearch.html') diff --git a/quicksearch.html b/quicksearch.html deleted file mode 100644 index 1b1ecb1a6..000000000 --- a/quicksearch.html +++ /dev/null @@ -1,151 +0,0 @@ - - - - - Bugzilla QuickSearch - - - - -

-If you are already familiar with the original -Bugzilla Query Form, -you may prefer this form. - -

- - - - -

Bugzilla QuickSearch

- -

-Type in one or more words (or word fragments) to search for: -

- - - - - -

Getting Started

- -

This is case-insensitive search. -
- table , Table - and TABLE are all the same.
-
This is all words as substrings search.
- Therefore you should use stems to get better results: -
- Use localiz instead of localize or - localization.
- Use bookmark instead of bookmarks or - bookmarking.
-

- -

Features

- -

Boolean operations: ``-foo''(NOT), ``foo bar''(AND), - ``foo|bar''(OR). -
- NOT: Use -foo to exclude bugs - with foo in the summary.
- AND: Space-separated words are treated as a conjunction.
- OR: Within a word, "|"-separated parts denote alternatives.
- Besides "|", a comma can be used to separate alternatives.
- OR has higher precedence than AND; AND is the top level operation
- Example: url,location bar,field -focus - means - (url OR location) AND (bar OR field) AND (NOT focus) -
-
Use +foo to search for bugs where the summary contains foo as a substring.
- Use #foo to search for bugs where the summary contains the word foo -
- +brow does not find all bugs in the Browser product
- #title does not find bugs bugs with titlebar or titled
- Phrases with special chars (space, comma, +, -, #, ...) can be quoted: -
- "lock icon"
-
-
Open vs. Resolved Bugs:
- By default, only open (i.e. unresolved) bugs are shown. - Use +DUP as first word in your query - to include duplicate bugs in your search, - FIXED to search for fixed bugs only, - or ALL to search all bugs, - regardless of status or resolution. Searching for duplicates is - recommended if you can't find an open bug directly. -
- +DUP,FIXED table border
- ALL mouse wheel
-
Focus the Search with Products & Components:
- To search for bugs in product "Foo Bar" only, add - :foo or :bar or both - to your query. - You can do this with any substring of a - product or component - to focus the search. -

- -

More Tips

- -

You can also use this tool to lookup a bug by its number. -
- 12345
-
A comma-separated list of bug numbers gives you a list of these bugs. -
- 12345,23456,34567
-

- -

-By default, the following fields are searched: Summary, Keywords, Product, -Component, Status Whiteboard. If a word looks like a part of a URL, that field -is included in the search, too. -

- -

-Use the powerful -Bugzilla Query Form -for advanced queries. -

- - - -- cgit v1.2.1