198408 - ui to find components and product based on short user text input

Status: RESOLVED FIXED

(Bugzilla :: Creating/Changing Bugs, enhancement, P2)

Description

[jean-georges lazarus]

User-Agent:       Mozilla/4.0 (compatible; MSIE 5.01; Windows 98)
Build Identifier: 

I need a small browser to seek the right component and product in the combined 
list of products and components from the knowing of any keywords.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

[Vlad Dascalu]

This could be related to bug 116952.

Comment 2

[Dave Miller [:justdave]]

Reassigning bugs that I'm not actively working on to the default component owner
in order to try to make some sanity out of my personal buglist.  This doesn't
mean the bug isn't being dealt with, just that I'm not the one doing it.  If you
are dealing with this bug, please assign it to yourself.

Comment 3

[jean-georges lazarus]

Some more informations : 
My request concerns the process creation of a bug. When reporters create bugs, 
they use the screen selection, that supposes that the reporter has a good 
knowledge of the hierarchy products-components. So, he can easely choose, first 
the product, after the component. Let us suppose that he does'nt know the 
product, he only knows the component, or worse, he knows only one key word of 
the description of a component. In this case it would be well to have a regex 
function search, which, by indicating a key word, search in the Products and 
Components - tables, the list of all the products or components, which contain 
in their title or descriptions, this key words. (Its seems like the function 
Search of Bugzilla in the bugs base : I indicate a word, and the search engine 
find all bugs that contain this word).

Comment 4

[Eyal Rozenberg]

*** Bug 333687 has been marked as a duplicate of this bug. ***

Comment 5

[Eyal Rozenberg]

Expanding scope of bug summary. Comment from dupe bug 333687:

When I submit a new bug, I am often unsure which component I should be filing
under, and which products contain which components. There could be some fast
all-client-side javascript search of a component list.

Alternatively, this could be done server-side, in which one could search for
components by words often appearing in bug summaries for that component, or
using some other method.

A third alternative would be to auto-suggest a component based on the rest of
the details of the bug and a sever-side search as defined above, i.e. you will
be able to first enter the bug details without choosing the component.

Comment 6

[Frédéric Buclin]

*** Bug 337549 has been marked as a duplicate of this bug. ***

Comment 7

[Max Kanat-Alexander]

Bugzilla 3.2 is now frozen. Only enhancements blocking 3.2 or specifically approved for 3.2 may be checked in to the 3.2 branch. If you would like to nominate your enhancement for Bugzilla 3.2, set the "blocking3.2" flag to "?". Then, either the target milestone will be changed back, or the blocking3.2 flag will be granted, if we will accept this enhancement for Bugzilla 3.2.

This particular bug has not been touched in over eight months, and thus is being retargeted to "---" instead of "Bugzilla 4.0". If you believe this is a mistake, feel free to retarget it to Bugzilla 4.0.

Comment 9

[David Lawrence [:dkl]]

Attachment: Patch to add search field for components in enter_bug.cgi (v1)

Hi Glob. Here is the code I was talking about that we added at Red Hat that filters the components based on name and/or description. Proof of concept but not exactly what we talked about or this bug but I wanted to let you see what I was talking about with working code.

dkl

Comment 10

[:glob ✱]

Comment on attachment 607344 [details] [diff] [review]
Patch to add search field for components in enter_bug.cgi (v1)

it's interesting, but as it doesn't include product searching it doesn't satisfy the requirements for this bug.

as it's a single field approach, i'm not sure how it could be extended to include product searching.

for enter bug, you need to be able to search by product-name/product-desc/component-name/component-desc before you select the product.

> === modified file 'js/create_bug.js'
looks like this is a bmo patch, as this file doesn't exist upstream.

Comment 11

[:glob ✱]

http://harthur.github.com/fileit/ has a nice approach to this.

Comment 12

[David Lawrence [:dkl]]

(In reply to Byron Jones ‹:glob› from comment #11)
> http://harthur.github.com/fileit/ has a nice approach to this.

Very nice. It's funny. After our conversation I put together a working prototype that does basically the same thing in extensions/BMO/template/en/default/global/choose-product.html.tmpl and now I see this. I will submit a patch for you to look at.

dkl

Comment 13

[David Lawrence [:dkl]]

Attachment: Patch to add search field for product/component to pretty product chooser (v2)

This patch adds a search field to the enter_bug.cgi product chooser page that allows a user to enter some keywords and give a list of product:component based on name or description. When a user selects a result then they are taken to the enter_bug.cgi entry form with the proper component already selected.

We could also add this to the guided page at some point.

Please review.
dkl

Comment 14

[David Lawrence [:dkl]]

Comment on attachment 616759 [details] [diff] [review]
Patch to add search field for product/component to pretty product chooser (v2)

Moved patch to BMO specific bug 747193.

Comment 15

[sjw]

Attachment: enter_bug.png

I already got a search UI. Was this fixed?

Comment 16

[David Lawrence [:dkl]]

This was implemented as an extension on bugzilla.mozilla.org and will not be implemented upstream as far as i know. So we can close this out.

Comment 17

[David Lawrence [:dkl]]

OK, reopening as we may do this eventually upstream if time allows. It will take some work to do as it is completely implemented in extension code.

dkl

Comment 18

[Kohei Yoshino [:kohei]]

Bugzilla 6.0 will be based on BMO, which means the upstream will also get the pretty product chooser.