buglist.cgi: nonexistant product or component produces empty list instead of error

NEW
Unassigned

Status

()

--
minor
12 years ago
6 years ago

People

(Reporter: mdb, Unassigned)

Tracking

Details

(URL)

(Reporter)

Description

12 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; de; rv:1.8.0.4) Gecko/20060617 Firefox/1.5.0.4
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.8.0.4) Gecko/20060617 Firefox/1.5.0.4

Hi,

buglist.cgi does not complain about non-existing products or components being queried and instead simply delivers an empty list, as if everythin in the query would be all right.

This hits us with Bugzilla links that are stored in documentation pages. When the product is renamed, the search will not find anything anymore.


I searched here for "component product missing", scanned all top-200 subjects, visited about 30-40 Bugs and the closest one I found was bug#233617 - but that bug's focus is on Bugzilla saved searches, which are stored on the bugzilla database and can be influenced by rename operations etc., so I consider this to be another bug.

Reproducible: Always

Steps to Reproduce:
Compare the following search results:

http://bugs.gentoo.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=commit&product=Bugzilla
http://bugs.gentoo.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=Test-Suchbegriff&product=Bugzilla
http://bugs.gentoo.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=commit&product=gibtesnicht

The first two are valid searches, the first one should find a thing, the second one should produce a valid empty list and the third one produces an invalid empty list instead of complaining "no such product 'gibtesnicht'".
Actual Results:  

with non-existent product delivers "no bugs found"

Expected Results:  
With non-existend product should complain "no such product 'gibtesnicht'".

With only one of component or product non-existent but the other one being valid, should at least add a note stating "no such { product | component } 'xyz'".

Comment 1

12 years ago
It should eventually say that the product either doesn't exist or that you are not allowed to view bugs in this product. Else you could use this way to determine which products are invalid and which ones are hidden.

Comment 2

12 years ago
Yep. Although I think instead of an error, perhaps we should just display a message at the top of the bug list. We could display an error if that would be easier to code, though.
Severity: normal → minor
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Buglist.cgi: nonexistant product or component produces empty list instead of error → buglist.cgi: nonexistant product or component produces empty list instead of error
Version: unspecified → 2.20
(Reporter)

Comment 3

12 years ago
Has there by any discussion / decision about what to do (raise an error or display "invalid permissions or empty list"), when invalid product / component was selected?

Regards,
Dominik
(Reporter)

Comment 4

12 years ago
As written in the Introduction of this bug, I read about 30-40 Bugs before posting this one.

AFAIK, the code fragments that I saw (or visited) was not trivial and required additional knowledge of other code fragments. Which leads me to believe that I'm not the best person to be that "Nobody's working on this yet, feel free to take it <query-and-buglist@bugzilla.bugs>".

I hope something will happen with this issue, maybe mkanat or LpSolit can do this.

Are there any updates on this issue?

Regards,
Dominik
You need to log in before you can comment on or make changes to this bug.