Changes between Version 1 and Version 2 of TracQuery
- Timestamp:
- 2011-01-15 11:32:15 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracQuery
v1 v2 7 7 8 8 == Filters == 9 When you first go to the query page the default filters will display all open tickets, or if you're logged in it will display open tickets assigned to you. 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 list in the bottom-right corner of the filters box. Filters with either a text box or a pulldown menu of options can be added multiple times to perform an ''or'' of the criteria. 9 10 When you first go to the query page the default filter will display tickets relevant to you: 11 * If logged in then all open tickets it will display open tickets assigned to you. 12 * If not logged in but you have specified a name or email address in the preferences then it will display all open tickets where your email (or name if email not defined) is in the CC list. 13 * If not logged and no name/email defined in the preferences then all open issues are displayed. 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. 10 16 11 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. … … 16 22 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 23 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.24 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 25 20 26 The query results can be refreshed and cleared of these status indicators by clicking the ''Update'' button again. … … 22 28 == Saving Queries == 23 29 24 While Trac does not yet allow saving a named query and somehow making it available in a navigable list, you can save references to queries in Wiki content, as described below. 30 Trac allows you to save the query as a named query accessible from the reports module. To save a query ensure that you have ''Updated'' the view and then click the ''Save query'' button displayed beneath the results. 31 You can also save references to queries in Wiki content, as described below. 32 33 ''Note:'' one way to easily build queries like the ones below, you can build and test the queries in the Custom report module and when ready - click ''Save query''. This will build the query string for you. All you need to do is remove the extra line breaks. 25 34 26 35 === Using TracLinks === … … 98 107 === Query Language === 99 108 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. 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 litteral `&` or `|` in a value, escape the character with a backslash (`\`). 101 110 102 111 The available operators are: … … 112 121 || '''`!$=`''' || the field content does not end with any of the values || 113 122 123 The date fields `created` and `modified` can be constrained by using the `=` operator and specifying a value containing two dates separated by two dots (`..`). 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. 124 || '''`created=2007-01-01..2008-01-01`''' || query tickets created in 2007 || 125 || '''`created=lastmonth..thismonth`''' || query tickets created during the previous month || 126 || '''`modified=1weekago..`''' || query tickets that have been modified in the last week || 127 || '''`modified=..30daysago`''' || query tickets that have been inactive for the last 30 days || 114 128 115 129 ----