Launchpad itself

Also affects search error - too many matches

Bug #471328 reported by Prateek Karandikar on 2009-11-02

This bug report is a duplicate of: Bug #255282: project name picker search / vocabulary is hard/impossible to use (too many results on exact searches). Edit Remove

This bug affects 6 people

Affects		Status	Importance	Assigned to	Milestone
	Launchpad itself	Triaged	High	Unassigned

Bug Description

Searching for products/projects/whatever-they're-called to mark as "also affects" often results in an unhelpful "Too many matches. Please try to narrow your search." , even while searching for something simple like Ubuntu. Take any non-Ubuntu bug and go to "also affects project", and try to mark it as affecting "ubuntu". That will fail, and searching for "ubuntu" will say that there are too many matches.

A task like this should just work and not frustrate the user. Searches should never fail: if there are zillions of results, at least display the most relevant ones.

(Aside: I just discovered that Ubuntu is apparently a *distribution*, and not a *project*. Who'd have known?)

Tags:

Deryck Hodge (deryck) on 2009-11-03

Changed in malone:
status:	New → Triaged
importance:	Undecided → High
tags:	added: bug-page ui
summary:	- Search - too many matches + Also affects search error - too many matches

Revision history for this message

Martin Pool (mbp) wrote on 2009-12-16:

vocab-broken.png Edit (143.2 KiB, image/png)

This is now blocking in <https://launchpad.net/bugs/496827> reassigning this bug from bzr-svn to bzr. This seems like a new and pretty serious regression.

Revision history for this message

Martin Pool (mbp) wrote on 2009-12-16:

I don't know if it's related but I do have

Error: Q.getElementsByTagName is not a function
Source File: https://staging.launchpad.net/+icing/rev8794/build/launchpad.js
Line: 4325

(and hundreds of warnings) in my js console.

This is quite but not perfectly reproducible in eg https://bugs.staging.launchpad.net/bzr/+bug/385879

Revision history for this message

Martin Pool (mbp) wrote on 2009-12-16:

Is there any non-ajax workaround?

Revision history for this message

Deryck Hodge (deryck) wrote on 2009-12-16:

Hi, Martin.

Sorry this is causing so much pain. Can you click the arrow pointing downward (the one like an upside down eject symbol) at the start of the bugtask table and enter the project name directly there once the entire form is revealed?

This is not helpful for the case where you do actually need to search for a project name, but in the case where the project name is known this should work.

I'll take a look tomorrow when I'm clear minded to see when we can get this scheduled.

Cheers,
deryck

Revision history for this message

Martin Pool (mbp) wrote on 2009-12-16: Re: [Bug 471328] Re: Also affects search error - too many matches

2009/12/16 Deryck Hodge <email address hidden>:
> Hi, Martin.
>
> Sorry this is causing so much pain. Can you click the arrow pointing
> downward (the one like an upside down eject symbol) at the start of the
> bugtask table and enter the project name directly there once the entire
> form is revealed?

Oh good point: yes, that's a good workaround, so this is fine.

In fact since I normally know the precise name of the thing I want to
assign to, I'll normally do this in future, because the picker doesn't
prioritize exact matches (for which there is another bug.)

> This is not helpful for the case where you do actually need to search
> for a project name, but in the case where the project name is known this
> should work.
>
> I'll take a look tomorrow when I'm clear minded to see when we can get
> this scheduled.

Thanks for the prompt response.

--
Martin <http://launchpad.net/~mbp/>