Changes between Version 1 and Version 2 of TracQuery


Ignore:
Timestamp:
10/22/08 03:31:28 (11 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracQuery

    v1 v2  
    2929{{{ 
    3030[query:status=new|assigned|reopened&version=1.0 Active tickets against 1.0] 
     31 
    3132}}} 
    3233 
     
    3940{{{ 
    4041[query:?status=new&status=assigned&status=reopened&group=owner Assigned tickets by owner] 
     42 
    4143}}} 
    4244 
     
    6163{{{ 
    6264[[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]] 
     65 
    6366}}} 
    6467 
     
    7073{{{ 
    7174[[TicketQuery(version=0.6|0.7&resolution=duplicate, count)]] 
     75 
    7276}}} 
    7377 
     
    7882=== Query Language === 
    7983 
    80 `query:` TracLinks and the `[[TicketQuery]]` macro both use a mini “query language” for specifying query filters. Basically, the filters are separate 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. 
     84`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. 
    8185 
    8286The available operators are: