behaviour of "is" query
|Reported by:||Owned by:|
I have experienced a case of the "is" query not behaving as I expected, so I will report it here in case anyone can think of a way to avoid this, or if perhaps a new query type would be desirable.
I will draw an example from the MacPorts trac install… when querying their tickets you often want to search for tickets filed against a specific port (the ports are the software packages that can be installed with macports). Sometimes there are similarly named ports, so it seemed to me that I could use the "is" query to find tickets filed against a specific port name. However, many tickets are filed against mutliple ports, such that their "Port" field is a space-separated list of port names. In this case, if you perform an "is" query, it will not match a ticket that is filed against your port of interest as well as other ports.
- ticket has Port field set to: "gimp2 gtk2"
- query for "Port is gimp2"
- fails to find the above ticket
I (now) understand how the query works, and perhaps it is the "fault" of the Macports team for using the field in this sense, but I wonder if there could be a query that would solve this sort of problem. Contains is ok, but also matches substrings, such as "gimp" in the above example.
This is not particularly important at all, just thought I would record it here in case anyone else is experiencing something similar…