Changes between Version 2 and Version 3 of TracQuery
- Timestamp:
- Dec 2, 2009, 12:08:12 AM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracQuery
v2 v3 85 85 [[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter)]] 86 86 87 ==== Full rows ==== 88 In ''table'' format you can also have full rows by using ''rows=<field>'' like below: 89 90 {{{ 91 [[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter,rows=description)]] 92 }}} 93 94 This is displayed as: 95 [[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter,rows=description)]] 96 87 97 88 98 === Query Language === 89 99 90 `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. 100 `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 (`\`). 91 101 92 102 The available operators are: … … 102 112 || '''`!$=`''' || the field content does not end with any of the values || 103 113 114 The date fields `created` and `modified` can be constrained by using the `=` operator and specifying a value containing two dates separated by a semicolon (`;`). Either end of the date range can be left empty, meaning that the corresponding end of the range is open. The date parser understands a few natural date specifications like "3 weeks ago", "last month" and "now", as well as Bugzilla-style date specifications like "1d", "2w", "3m" or "4y" for 1 day, 2 weeks, 3 months and 4 years, respectively. Spaces in date specifications can be left out to avoid having to quote the query string. 115 || '''`created=2007-01-01;2008-01-01`''' || query tickets created in 2007 || 116 || '''`created=lastmonth;thismonth`''' || query tickets created during the previous month || 117 || '''`modified=1weekago;`''' || query tickets that have been modified in the last week || 118 || '''`modified=;30daysago`''' || query tickets that have been inactive for the last 30 days || 104 119 105 120 ----