prior to 4.0, the following URL worked: https://bugzilla.mozilla.org/buglist.cgi?product=Core&product=Firefox&product=Toolkit&bug_status=UNCONFIRMED%2CNEW%2CASSIGNED%2CREOPENED%2CRESOLVED&chfield=[Bug%20creation]&chfieldfrom=-24h&order=Bug%20Number&list_id=678 4.0 expects multiple bug_status fields.. https://bugzilla.mozilla.org/buglist.cgi?product=Core&product=Firefox&product=Toolkit&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&chfield=[Bug%20creation]&chfieldfrom=-24h&order=Bug%20Number&list_id=678

Who is using URLs of the former form? Has Bugzilla ever generated them or suggested that they be supported? I suspect this is a result of the fix to the bug which prevented commas being valid in various fields. Gerv

The URL given was based on the old "Bugs Filed Today" link that at least one point in time was shown on BMO.

(In reply to comment #1) > Who is using URLs of the former form? Has Bugzilla ever generated them or > suggested that they be supported? > http://www.mozillazine.org/rd/mzbg/ for one.

Actually, it's worse than that. Typing "status:conf" in the QuickSearch bar has no effect. It's broken in 4.0 but is working fine in 3.6 and 4.1. No idea what regressed this. mkanat, do you have an idea?

The bug that glob originally reported here is an intentional change in behavior, not a bug. It's the fix for "can't search for products (etc.) with commas in their names" bug. That behavior won't be reverted--the fact that it ever worked was largely a bug (although a bug that has been present for a very long time). As far as the problem with QS, that sounds like a separate bug that should be filed separately.

Then the documentation needs to be updated accordingly. https://bugzilla.mozilla.org/page.cgi?id=quicksearch.html says that: "If you want to search specific fields, you do it like field:value, where field is one of the field names lower down in this document and value is the value you want to search for in that field. If you put commas in the value, then it is interpreted as a list of values, and bugs that match any of those values will be searched for."

(In reply to comment #5) > The bug that glob originally reported here is an intentional change in > behavior, not a bug. It's the fix for "can't search for products (etc.) with > commas in their names" bug. Also, IMO this implementation is bad. It should only consider commas as part of the field value if you use quotes. Else it should see them as a field value separator.

Oh wait, I mixed both issues. I will file a separate bug for QS. :)