Invalid statuses in search now ignored rather than honoured?

Gervase Markham gerv at
Tue Sep 28 09:26:27 UTC 2010

On 27/09/10 23:51, Max Kanat-Alexander wrote:
> On 09/27/2010 11:02 AM, Gervase Markham wrote:
>> Can I ask: is this an intentional change?
> 	More or less, yes. Here's where it happened:

OK. So I think this behaviour makes those fields inconsistent with all 
the others in terms of their behaviour.

In the case of other fields, such as component, platform, op_sys, or 
custom fields, fieldname=Sproink will not match anything. In the case of 
these fields for which you have changed the behaviour, status=Sproink 
will match everything, including things whose status is not Sproink.

I think the inconsistency is bad, and that the former behaviour is the 
preferable one for all fields. Would it be possible to restore it 
without removing the optimization added in the above bug?

dev-apps-bugzilla mailing list
dev-apps-bugzilla at

More information about the developers mailing list