Red Hat Bugzilla – Bug 140685
Issues with bugzilla search
Last modified: 2013-06-23 23:02:22 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2)
Description of problem:
Bugzilla search results
a) Should not open a new page
b) If you insist on a new page, don't make it a targetted new page so
one can keep old results.
c) Should have a "new" link at the bottom of the list of known bugs to
open a new report on the selected product.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Actual Results: N/a
Expected Results: N/a
Thanks for the feedback. I will see if I can get your suggestions in by the final cut.
I now have time to address this further and am also trying to get the beta
rolled out to production use very soon. Where is the search that you are
referring to? Are you talking about from the Guided bug entry page where you can
do a simple search of bugs before entering a new one?
I don't recall just what I was doing over three months ago.
I suffer a slow dialup connexion, and resent any behaviour that takes more of
my time than I think reasonable. Misbehaviour includes popping unexpected
windows, forcing me to <click><click><click> to hunt round to find feedback
I _think_ what happened is that I checked a list of bugs, didn't find one that
matched my problem and couldn't see an easy way to create a new report based
on the information BZ had.
Something not particularly connected woth my original report that happened in
the past few days is I found a bug report that exactly matched a problem I
had, was closed "wontfix" because the original reporter couldn't provide
needed information, and I couldn't reopen it because I was not the original
reporter, the assignee or a "trusted person." I had instead to create a new
BZ is chock full of inconveniences like this. And seems slow to boot.
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.
Please file with the upstream bugzilla https://bugzilla.mozilla.org/ is still an issue.