Red Hat Bugzilla – Bug 81733
query page UI
Last modified: 2013-06-23 23:10:08 EDT
The query page ( https://bugzilla.redhat.com/bugzilla/query.cgi ) design is not
First , the "Quick Search". One would expect tha this is separate form the rest
of search elements, but it is not. Clicking on the "Search" button in "Quick
Search" is the same as clicking "Search" in the "Query Action" section. This is
a bit unintuitive.
Second , when skipping Quck Search and using the rest, in the "String Search"
section , there is no entry for searching in the bug Summaries. One must use
the Summary field in "Quick Search". This again is not very user friendly.
I recommend adding a "Summary" field to "String Search".
About "Quick Search" , either :
- put a note that it will also be influenced by the search criteria below
- make is separate from the other search criteria ( search _only_ by the
When I enter "contains all of the words/strings" and "firstboot Time" in Quick
Search, I don't find the bug I'm looking for - 82061. Maybe Quick Search
doesn't consider closed bugs worth searching for. There are about 10 duplicate
bugs reported against Phoebe and firstboot because a default query doesn't show
you 82061. It may be complicated, but if Quick Search could also show bugs that
have been closed for less than 30 days, I think a lot of duplicates could be
Fred, that is becasue bug 82061 does not have the words "firstboot Time" in
its "Summary" field. Its Summary is "Traceback loading Date and Time module",
you can find it by entering for example "traceback date time". You must also
select "CLOSED" in the "Status" or set nothing in "Status", becasue the default
is ti search for bugs that have Status NEW, ASSIGNED or REOPENED.
Red Hat's current Bugzilla version is 2.18. I am moving all older open bugs to
this version. Any bugs against the older versions will need to be verified that
they are still bugs. This will help me also to sort them better.
Red Hat Bugzilla is now using version 3.2 of the Bugzilla codebase and therefore this bug will need to be re-verified against the new release. With the updated code this bug may no longer be relevant or may have been fixed in the new code.
Updating bug version to 3.2.
This bug is no more relevant to bugzilla 3.2 , as the Search pages have completely changed in design and the don't include the sections mentioned in that bug report any more. So problems mentioned in this report are considered solved in the current bugzilla release.