== Choosing good keywords for tickets ==

Trac can search the full text of tickets, so adding a keyword that already occurs in another field doesn't help for general searching. If we standardise the use of certain keywords, however, it could make finding certain specific types of ticket much easier. This, then, is a suggested list of keywords that we might like to standardise.

||= '''Keyword''' =||= '''Meaning''' =||
|| [query:status=assigned&status=new&status=reopened&keywords=~tiger&order=priority tiger]\\`leopard`\\[query:status=assigned&status=new&status=reopened&keywords=~snowleopard&order=priority snowleopard]\\`lion`\\[query:status=assigned&status=new&status=reopened&keywords=~mountainlion&order=priority mountainlion] || The ticket is only applicable to the indicated OS release(s). ||
|| [query:keywords=~i386&col=id&col=summary&col=keywords&col=status&col=owner&col=type&col=priority&order=priority i386]\\[query:keywords=~x86_64&col=id&col=summary&col=keywords&col=status&col=owner&col=type&col=priority&order=priority x86_64]\\`ppc`\\[query:keywords=~ppc64&col=id&col=summary&col=keywords&col=status&col=owner&col=type&col=priority&order=priority ppc64] || The ticket is only applicable when using the indicated `build_arch`. ||
|| [query:keywords=~LP64&col=id&col=summary&col=keywords&col=status&col=owner&col=type&col=priority&order=priority LP64] || The ticket describes a problem caused by the size of variables of type int, long or pointers on a 64-bit arch. ||

{{{
#!comment
TODO: find out how to do a query for "leopard" that does NOT also include "snowleopard", for "lion" that does NOT also include "mountainlion", and for "ppc" that does NOT also include "ppc64"
}}}