Is this possible? So I could query [pp] and still get all the [PP] bugs?

Yes, it's possible. It's the usual tradeoff between making the UI simple and making it powerful. I'm toying with the idea of changing the text queries to have a UI very similar to the email-address queries.

Sound great. The new fields and product/component work would take higher priority for me though. Whenever you can get around to this...cool.

Well, yes...it's also a usability issue for internal bugzilla users, since the behavior differs from that of bugsplat, which doesn't do case sensitivity for queries. Thus, QA folks have spent a lot of time accidentally writing up bugs that are already in BugZilla, since the query failed due to a difference in case sensitivity, and not everyone knows how to use regular expressions.

Setting all current Open/Normal to M4.

Clearing "M" field since Webtools product is not used for 5.0 specific project bug metrics and will mess up our queries on milestones.

terry, folks externally and internally making mistakes with their queries. Is this one an easy one to fix? Would be totally awesome if you can do. :-)

Not completely easy, but I agree it oughter be done.

Reassigning to dmose@mozilla.org, who now has front-line responsibility for all Bonsai and Bugzilla bugs.

Reassigning back to me. That stuff about me no longer being the front-line person responsible for Bugzilla and Bonsai turned out to be short-lived. Please pardon our confusion, and I'm very sorry about the spam.

Bug #6677 is a duplicate of this bug, except that I have provided a patch which (IMHO) provides 90% of the solution that users want. I.e. to always have string searches a case sensitive. Another patch I submitted for bug #6411 make the RADIO widget a SELECT widget. Thus if that patch is also applied, it should be a very simple modification to add "case-sensitive substring" to "substring" if you wanted to differentiate. Though I believe, most users would use a caseless substring, and it should be the default.

I do in fact think that this bug is a duplicate of bug 6677, which is now fixed. *** This bug has been marked as a duplicate of 6677 ***

moving to Bugzilla product reassign to default owner/qa for INVALID/WONTFIX/WORKSFORME/DUPLICATE