Searching for bug numbers should work even as part of complex search string

[Wouter van Heyst]

Trying to weed down the list of subscribed bugs, I first search on

 'variant | nicks'

Which nicely gets me bugs 29800 and 50466, so far, so good.
However, when I search for '29800 | nicks' or 'nicks | 29800' I only get back bug 50466 'branch nicks are poorly explained'.

A bugnumber by itself directly jumps to the bug in question.

[Matthew Paul Thomas (mpt)]

Wouter, what did you expect to get from the '29800 | nicks' search? Did you expect bug 29800 to be included? (I suppose that might be a cheap way of letting people link to custom lists of bugs: search for their numbers with the or operator.)

[Wouter van Heyst (larstiq)]

On Thu, Jan 04, 2007 at 01:56:01AM -0000, Matthew Paul Thomas wrote:
> Wouter, what did you expect to get from the '29800 | nicks' search? Did
> you expect bug 29800 to be included? (I suppose that might be a cheap
> way of letting people link to custom lists of bugs: search for their
> numbers with the or operator.)

Yup. In this case I wanted to confirm that a certain bug and it's
duplicate were not in my subscribedbugs listing, even though I am
subscribed. For a screenshot to illustrate the problem the entire list
is a bit much (and more than one page), so I wanted to restrict it to
the two bugs in question (or nothing to prove my point). Testing it with
'29800 | 50466' showed that it didn't work though :/

Wouter van Heyst

[Morten Kjeldgaard (mok0)]

... or there could simply be a separate field to search for bug #'s

[Gary Poster (gary)]

The use case might be valuable. I'm not convinced the solution is the right one for the use case. This bug is honestly unlikely to be addressed without community contributions (at which point it would have to have UI approval before proceeding). I'll leave it as "Triaged: Low" to indicate that the use case is interesting, at least.