Was talking about this recently with Sylvestre. Currently we have 5 types of bug searches, and we want to remove this redundancy: * Quick Search (from the global header or homepage) * [Instant Search](https://bugzilla.mozilla.org/query.cgi?format=instant) * [Simple Search](https://bugzilla.mozilla.org/query.cgi?format=specific) * [Advanced Search](https://bugzilla.mozilla.org/query.cgi?format=advanced) * [Google Search](https://bugzilla.mozilla.org/query.cgi?format=google) ## Quick Search My plan is constantly improving the Quick Search bar on the global header. The bug to [add history, keywords, components to the search results](https://bugzilla.mozilla.org/show_bug.cgi?id=1472565) is blocked by CI test failures though. ## Instant Search This page is not popular according to GA, though the “find as you type” functionality seems useful. ## Simple Search An interesting fact I’ve just found on GA: somehow this page is quite popular, earning 2x page views than Advanced Search. Since GA is not logging the activity of many (advanced) users, the data we can see here isn’t accurate at all, but it’s obviously a surprise, and I have no idea how this could happen. The thing is, results from Simple Search is not great when the term contains more than 2 words apparently because it’s an OR search. Compare these results of “print crash”: * [Quick Search](https://bugzilla.mozilla.org/buglist.cgi?quicksearch=print%20crash) * [Simple Search](https://bugzilla.mozilla.org/buglist.cgi?query_format=specific&order=relevance%20desc&bug_status=__open__&content=print%20crash&comments=0) * [Advanced Search](https://bugzilla.mozilla.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=print%20crash&resolution=---&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&classification=Other&query_format=advanced) So basically we can say people should simply use Quick Search instead. ## Advanced Search This page is crucial for advanced users, but it has to be improved. ## Google Search This is the least popular search page. Search by Google is convenient thanks to the fuzzy matching, but as noted on the page, not all bugs are indexed. Also, the results contain old, closed bugs, so it’s actually not that useful. It should be safe to remove this page. ## What’s Next I’m thinking of the following actions: * Integrate the Instant Search (actually [possible duplicates](https://bmo.readthedocs.io/en/latest/api/core/v1/bug.html#possible-duplicates)) to the global header’s Quick Search, so results will be displayed almost instantly in the dropdown list * Add dropdown-style search options, Status and Product in particular, to the global header’s Quick Search, like [Google Drive](https://www.cnet.com/how-to/hidden-features-of-google-drive/) * Remove the tab navigation from the search pages * Remove the content from the Instant, Advanced and Google Search pages * Add a message to the Instant and Advanced pages, say, use Quick Search instead * Add a message to the Google Search page, say, this page has been removed * Conduct an UX analysis of the Advanced Search page
Bug 1525709 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Was talking about this recently with Sylvestre. Currently we have 5 types of bug searches, and we want to remove this redundancy: * Quick Search (from the global header or homepage) * [Instant Search](https://bugzilla.mozilla.org/query.cgi?format=instant) * [Simple Search](https://bugzilla.mozilla.org/query.cgi?format=specific) * [Advanced Search](https://bugzilla.mozilla.org/query.cgi?format=advanced) * [Google Search](https://bugzilla.mozilla.org/query.cgi?format=google) ## Quick Search My plan is constantly improving the Quick Search bar on the global header. The bug to [add history, keywords, components to the search results](https://bugzilla.mozilla.org/show_bug.cgi?id=1472565) is blocked by CI test failures though. ## Instant Search This page is not popular according to GA. While the “find as you type” functionality seems useful, the [possible duplicates](https://bmo.readthedocs.io/en/latest/api/core/v1/bug.html#possible-duplicates) includes very old closed bugs, which makes results useless in some cases. ## Simple Search An interesting fact I’ve just found on GA: somehow this page is quite popular, earning 2x page views than Advanced Search. Since GA is not logging the activity of many (advanced) users, the data we can see here isn’t accurate at all, but it’s obviously a surprise, and I have no idea how this could happen. The thing is, results from Simple Search is not great when the term contains more than 2 words apparently because it’s an OR search. Compare these results of “print crash”: * [Quick Search](https://bugzilla.mozilla.org/buglist.cgi?quicksearch=print%20crash) * [Simple Search](https://bugzilla.mozilla.org/buglist.cgi?query_format=specific&order=relevance%20desc&bug_status=__open__&content=print%20crash&comments=0) * [Advanced Search](https://bugzilla.mozilla.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=print%20crash&resolution=---&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&classification=Other&query_format=advanced) So basically we can say people should simply use Quick Search instead. ## Advanced Search This page is crucial for advanced users, but it has to be improved. ## Google Search This is the least popular search page. Search by Google is convenient thanks to the fuzzy matching, but as noted on the page, not all bugs are indexed. Also, the results contain old, closed bugs, so it’s actually not that useful. It should be safe to remove this page. ## What’s Next I’m thinking of the following actions: * Integrate the Instant Search (actually [possible duplicates](https://bmo.readthedocs.io/en/latest/api/core/v1/bug.html#possible-duplicates)) to the global header’s Quick Search, so results will be displayed almost instantly in the dropdown list * Add dropdown-style search options, Status and Product in particular, to the global header’s Quick Search, like [Google Drive](https://www.cnet.com/how-to/hidden-features-of-google-drive/) * Remove the tab navigation from the search pages * Remove the content from the Instant, Advanced and Google Search pages * Add a message to the Instant and Advanced pages, say, use Quick Search instead * Add a message to the Google Search page, say, this page has been removed * Conduct an UX analysis of the Advanced Search page