Changes between Version 2 and Version 3 of TracQuery


Ignore:
Timestamp:
Feb 13, 2011 9:57:06 AM (4 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracQuery

    v2 v3  
    1313 * If not logged and no name/email defined in the preferences then all open issues are displayed. 
    1414 
    15 Current filters can be removed by clicking the button to the right with the minus sign on the label.  New filters are added from the pulldown lists at the bottom corners of the filters box ('And' conditions on the left, 'Or' conditions on the right).  Filters with either a text box or a pulldown menu of options can be added multiple times to perform an ''or'' of the criteria. 
     15Current filters can be removed by clicking the button to the left with the minus sign on the label.  New filters are added from the pulldown lists at the bottom corners of the filters box ('And' conditions on the left, 'Or' conditions on the right).  Filters with either a text box or a pulldown menu of options can be added multiple times to perform an ''or'' of the criteria. 
    1616 
    1717You can use the fields just below the filters box to group the results based on a field, or display the full description for each ticket. 
     
    7575  [[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]] 
    7676 
    77 Finally if you wish to receive only the number of defects that match the query using the ``count`` parameter. 
     77Finally, if you wish to receive only the number of defects that match the query, use the ``count`` parameter. 
    7878 
    7979{{{ 
     
    107107=== Query Language === 
    108108 
    109 `query:` TracLinks and the `[[TicketQuery]]` macro both use a mini “query language” for specifying query filters. Basically, the filters are separated by ampersands (`&`). Each filter then consists of the ticket field name, an operator, and one or more values. More than one value are separated by a pipe (`|`), meaning that the filter matches any of the values. To include a litteral `&` or `|` in a value, escape the character with a backslash (`\`). 
     109`query:` TracLinks and the `[[TicketQuery]]` macro both use a mini “query language” for specifying query filters. Basically, the filters are separated by ampersands (`&`). Each filter then consists of the ticket field name, an operator, and one or more values. More than one value are separated by a pipe (`|`), meaning that the filter matches any of the values. To include a literal `&` or `|` in a value, escape the character with a backslash (`\`). 
    110110 
    111111The available operators are: 
    112 || '''`=`''' || the field content exactly matches the one of the values || 
     112|| '''`=`''' || the field content exactly matches one of the values || 
    113113|| '''`~=`''' || the field content contains one or more of the values || 
    114114|| '''`^=`''' || the field content starts with one of the values ||