Changes between Version 1 and Version 2 of TracQuery
- Timestamp:
- Feb 24, 2010 5:37:18 PM (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracQuery
v1 v2 16 16 Clicking on one of the query results will take you to that ticket. You can navigate through the results by clicking the ''Next Ticket'' or ''Previous Ticket'' links just below the main menu bar, or click the ''Back to Query'' link to return to the query page. 17 17 18 You can safely edit any of the tickets and continue to navigate through the results using the ''Next/Previous/Back to Query'' links after saving your results. When you return to the query ''any tickets which w asedited'' will be displayed with italicized text. If one of the tickets was edited such that [[html(<span style="color: grey">it no longer matches the query criteria </span>)]] the text will also be greyed. Lastly, if '''a new ticket matching the query criteria has been created''', it will be shown in bold.18 You can safely edit any of the tickets and continue to navigate through the results using the ''Next/Previous/Back to Query'' links after saving your results. When you return to the query ''any tickets which were edited'' will be displayed with italicized text. If one of the tickets was edited such that [[html(<span style="color: grey">it no longer matches the query criteria </span>)]] the text will also be greyed. Lastly, if '''a new ticket matching the query criteria has been created''', it will be shown in bold. 19 19 20 20 The query results can be refreshed and cleared of these status indicators by clicking the ''Update'' button again. … … 29 29 {{{ 30 30 [query:status=new|assigned|reopened&version=1.0 Active tickets against 1.0] 31 32 31 }}} 33 32 … … 40 39 {{{ 41 40 [query:?status=new&status=assigned&status=reopened&group=owner Assigned tickets by owner] 42 43 41 }}} 44 42 … … 48 46 === Using the `[[TicketQuery]]` Macro === 49 47 50 The TicketQuerymacro lets you display lists of tickets matching certain criteria anywhere you can use WikiFormatting.48 The [trac:TicketQuery TicketQuery] macro lets you display lists of tickets matching certain criteria anywhere you can use WikiFormatting. 51 49 52 50 Example: … … 63 61 {{{ 64 62 [[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]] 65 66 63 }}} 67 64 … … 73 70 {{{ 74 71 [[TicketQuery(version=0.6|0.7&resolution=duplicate, count)]] 75 76 72 }}} 77 73 … … 79 75 [[TicketQuery(version=0.6|0.7&resolution=duplicate, count)]] 80 76 77 === Customizing the ''table'' format === 78 You can also customize the columns displayed in the table format (''format=table'') by using ''col=<field>'' - you can specify multiple fields and what order they are displayed by placing pipes (`|`) between the columns like below: 79 80 {{{ 81 [[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter)]] 82 }}} 83 84 This is displayed as: 85 [[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter)]] 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 81 97 82 98 === Query Language === 83 99 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. 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 (`\`). 85 101 86 102 The available operators are: 87 || ''' =''' || the field content exactly matches the one of the values ||88 || ''' ~=''' || the field content contains one or more of the values ||89 || ''' !^=''' || the field content starts with one of the values ||90 || ''' $=''' || the field content ends with one of the values ||103 || '''`=`''' || the field content exactly matches the one of the values || 104 || '''`~=`''' || the field content contains one or more of the values || 105 || '''`^=`''' || the field content starts with one of the values || 106 || '''`$=`''' || the field content ends with one of the values || 91 107 92 108 All of these operators can also be negated: 93 || '''!=''' || the field content matches none of the values || 94 || '''!~=''' || the field content does not contain any of the values || 95 || '''!!^=''' || the field content does not start with any of the values || 96 || '''!$=''' || the field content does not end with any of the values || 109 || '''`!=`''' || the field content matches none of the values || 110 || '''`!~=`''' || the field content does not contain any of the values || 111 || '''`!^=`''' || the field content does not start with any of the values || 112 || '''`!$=`''' || the field content does not end with any of the values || 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 || 97 119 98 120 ----