Bug search pages should document valid search expressions
Bug #660283 reported by
Nathan Stratton Treadway
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
When I go to one of the search-bug-reports pages (e.g. either
https:/
or
https:/
), I'm presented with a plain text box in front of the "Search" button... with no information at all about what sort of search expressions I can use.
There should be some search help provided, either right there on the search form page, or on a separate page pointed to by a "Search Help" link found on those forms (preferablly placed right next to the search box).
Revision history for this message
| Nathan Stratton Treadway (nathanst) wrote | #1 |
| Changed in malone: | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| Changed in launchpad: | |
| importance: | Medium → Low |
| tags: | added: docs search |
| tags: | added: bugs |
Revision history for this message
| Daira Hopwood (daira) wrote | #2 |
| tags: | added: bug-search |
To post a comment you must log in.
I searched around in the Launchpad Help > Bugs section, but didn't find any page that discusses the supported search expressions. (Obviously, if such a page already exists, then this bug is really just a request to have a direct link to that page from the search form.)
Most of what I now (think I) know about the Malone search expressions I've gathered from a few tests I've run myself, and from hints I've gleaned reading through other bug-search-related bugs reported here... but from what I've gathered, here are a few examples of items that seem like they should be documented:
* the system will search within the bug summaries and descriptions, but comments are not always included
* the system will look for bugs that include all of the words entered in the search-text box; the order of the search words does not matter
* there is no way to search for an exact phrase, or to exclude bugs that contain certain words
* entering a plain number into the search box will return just the bug with the given bug number
* the "|" character can be used to indicate a logical OR