Changes between Version 5 and Version 6 of TracQuery
- Timestamp:
- 04/04/2011 10:03:23 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracQuery
v5 v6 13 13 * If not logged and no name/email defined in the preferences then all open issues are displayed. 14 14 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.15 Current 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. 16 16 17 17 You 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. … … 75 75 [[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]] 76 76 77 Finally if you wish to receive only the number of defects that match the query usingthe ``count`` parameter.77 Finally, if you wish to receive only the number of defects that match the query, use the ``count`` parameter. 78 78 79 79 {{{ … … 107 107 === Query Language === 108 108 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 lit teral `&` 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 (`\`). 110 110 111 111 The available operators are: 112 || '''`=`''' || the field content exactly matches theone of the values ||112 || '''`=`''' || the field content exactly matches one of the values || 113 113 || '''`~=`''' || the field content contains one or more of the values || 114 114 || '''`^=`''' || the field content starts with one of the values ||