Changes between Version 3 and Version 4 of TracQuery
- Timestamp:
- May 19, 2008, 10:20:33 PM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracQuery
v3 v4 29 29 {{{ 30 30 [query:status=new|assigned|reopened&version=1.0 Active tickets against 1.0] 31 31 32 }}} 32 33 … … 39 40 {{{ 40 41 [query:?status=new&status=assigned&status=reopened&group=owner Assigned tickets by owner] 42 41 43 }}} 42 44 … … 61 63 {{{ 62 64 [[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]] 65 63 66 }}} 64 67 … … 70 73 {{{ 71 74 [[TicketQuery(version=0.6|0.7&resolution=duplicate, count)]] 75 72 76 }}} 73 77 … … 78 82 === Query Language === 79 83 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. 81 85 82 86 The available operators are:
