266639 - search returning only one single result should go directly to that bug

Status: RESOLVED WONTFIX

(Bugzilla :: Query/Bug List, enhancement)

Description

[Tobias Sager]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20041026 Firefox/1.0RC1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20041026 Firefox/1.0RC1

It would be nice if a search finding only one matching bug would
load that bug directly instead of displaying the buglist.

Reproducible: Always
Steps to Reproduce:
1. Search for a bug yielding only one result

Actual Results:  
Buglist with only one bug in it is displayed.

Expected Results:  
Go to the bug directly.

Comment 1

[Dave Miller [:justdave]]

Reassigning bugs that I'm not actively working on to the default component owner
in order to try to make some sanity out of my personal buglist.  This doesn't
mean the bug isn't being dealt with, just that I'm not the one doing it.  If you
are dealing with this bug, please assign it to yourself.

Comment 2

[Max Kanat-Alexander]

I've thought about doing this, too. pyrzak, LpSolit, any thoughts?

Comment 3

[Guy Pyrzak]

It does save one click, it could also be confusing unless a user knows that's what Bugzilla is doing for them. Firefox did this in 4.0, made it so that typing a query into the address bar did an "i'm feeling lucky search" instead of a normal search, and I  personally couldn't stand it. But I guess lots of people like it because it's the default 4.0 behavior.

I guess I'm saying I personally am not a huge fan, but I also don't think my personal opinion is necessarily the correct one on this topic.

I think if there was a message on the bug that the search automatically took you to that said "your search resulted in only one item so we took you to it, to view the search results list click here". That way people can still do the other things that appear on the search result page like save this search, create an atom feed etc.

Comment 4

[Frédéric Buclin]

(In reply to comment #2)
> I've thought about doing this, too. pyrzak, LpSolit, any thoughts?

I have no strong opinion. I agree with pyrzak that it's important to still be able to execute normal actions you can usually do from buglist.cgi, like saving the search or editing columns.

As a heavy triager, I often just need to know whether a bug already exists, not its content. In that case, this feature isn't useful to me. But I think it may still make sense, most of the time.

Comment 5

[:glob ✱]

as this would make it impossible to perform buglist related actions (such as saving), we shouldn't redirect.