Searching for "upstream" or product name doesn't do anything

[Matthew Paul Thomas]

<https://launchpad.net/products/malone/+bugs?field.searchtext=upstream> returns all the same results as <https://launchpad.net/products/malone/+bugs>. This is wrong, because most of those bug reports don't mention upstream anything.

Similarly, <https://launchpad.net/products/malone/+bugs?field.searchtext=malone> returns all the same results as <https://launchpad.net/products/malone/+bugs>. This makes it hard for me to find the bug report about Malone making it difficult to report bugs about Malone itself.

[Brad Bollenbach (bradb)]

On 12/14/05, Matthew Paul Thomas <email address hidden> wrote:
> Public bug reported:
> https://launchpad.net/malone/bugs/5782
>
> Affects: malone (upstream)
> Severity: Normal
> Priority: (none set)
> Status: New
>
> Description:
> <https://launchpad.net/products/malone/+bugs?field.searchtext=upstream&search=Search&orderby=-priority
> %2C-severity&field.milestone_assignment=&field.milestone_assignment-
> empty-marker=1> returns all the same results as
> <https://launchpad.net/products/malone/+bugs>. This is wrong, because
> most of those bug reports don't mention upstream anything.

This is due to the targetnamecache we use to make it easy to search on
the target name of the bug task. Since upstream bugtasks' target name
includes the word "upstream" a search for the word "upstream" will
return a lot of false positives.

Cheers,

--
Brad Bollenbach

[Matthew Paul Thomas (mpt)]

Partly fixed in RF 4610: "upstream" will no longer be included in the bug target names, so searching for it should work. However, the bug target names still should not be included in the bug's searchable text at all.

[Deryck Hodge (deryck)]

I believe this is fixed now. If not, please re-open.