how do i find bugs where QA Contact is not set?

Tyler tyler at
Tue Oct 12 23:15:43 UTC 2004

On Tue, Oct 12, 2004 at 07:03:37PM -0400, David Miller wrote:
> Christopher Hicks wrote:
> >On Tue, 12 Oct 2004, Tyler wrote on webtools:
> >
> >>Boolean queries for "contains ---", "contains [nothing -- that is, 
> >>nothing typed in the text box]", "doesn't match regex [a-z]", etc. 
> >>don't find these bugs. Ideas?
> >
> >I tried this and couldn't find a solution, but even more interesting: I 
> >tried the same "doesn't match regexp" string of "chicks" for bug owner 
> >and qa contact and it worked with bug owner, but qa contact.  I looked 
> >through the open and resolved bugzilla bugs and didn't see anything that 
> >seemed to address this.  Is it a known issue?  I'd like to give this guy 
> >some answer -- even if it points to a new bug yet to be created.

I was terribly confused as to why i'd been demoted to third-person
status until i noticed that this bounced over to developers@ (i proc all
my bugzilla mail to a single folder).

> Needs Bugzilla 2.19.1 or later to be able to do that from the UI (or a 
> recent version from CVS, since 2.19.1 isn't out yet).

Joel pointed me to
I'm waiting on an alluded-to-but-not-in-the-bug final patch for this.

> The problem is that the QA Contact field is null when it's empty, and 
> there's no provision in the UI to match a null (which is a distinct 
> entity from an empty string).
> 2.19cvs adds a "not" operator (as a checkbox) in front of each row of 
> the boolean chart.  You can then search for
> NOT ('QA Contact' 'matches regexp' '.')
> and successfully match it.

How would the NOT operator be different from "doesn't match regexp"?

Also, everything =~ /./ (except, evidently, the null that QA
Contact has by default), so why would !~ /./ be helpful?


More information about the developers mailing list