| 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 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. |
| 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. |
| | 34 | |
| | 35 | ''Note:'' you must have the '''REPORT_CREATE''' permission in order to save queries to the list of default reports. The ''Save query'' button will only appear if you are logged in as a user that has been granted this permission. If your account does not have permission to create reports, you can still use the methods below to save a query. |
| | 36 | |
| | 95 | === Customizing the ''table'' format === |
| | 96 | 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: |
| | 97 | |
| | 98 | {{{ |
| | 99 | [[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter)]] |
| | 100 | }}} |
| | 101 | |
| | 102 | This is displayed as: |
| | 103 | [[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter)]] |
| | 104 | |
| | 105 | ==== Full rows ==== |
| | 106 | In ''table'' format you can also have full rows by using ''rows=<field>'' like below: |
| | 107 | |
| | 108 | {{{ |
| | 109 | [[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter,rows=description)]] |
| | 110 | }}} |
| | 111 | |
| | 112 | This is displayed as: |
| | 113 | [[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter,rows=description)]] |
| | 114 | |
| 83 | | || '''=''' || the field content exactly matches the one of the values || |
| 84 | | || '''~=''' || the field content contains one or more of the values || |
| 85 | | || '''!^=''' || the field content starts with one of the values || |
| 86 | | || '''$=''' || the field content ends with one of the values || |
| | 121 | || '''`=`''' || the field content exactly matches one of the values || |
| | 122 | || '''`~=`''' || the field content contains one or more of the values || |
| | 123 | || '''`^=`''' || the field content starts with one of the values || |
| | 124 | || '''`$=`''' || the field content ends with one of the values || |
| 89 | | || '''!=''' || the field content matches none of the values || |
| 90 | | || '''!~=''' || the field content does not contain any of the values || |
| 91 | | || '''!!^=''' || the field content does not start with any of the values || |
| 92 | | || '''!$=''' || the field content does not end with any of the values || |
| | 127 | || '''`!=`''' || the field content matches none of the values || |
| | 128 | || '''`!~=`''' || the field content does not contain any of the values || |
| | 129 | || '''`!^=`''' || the field content does not start with any of the values || |
| | 130 | || '''`!$=`''' || the field content does not end with any of the values || |
| | 131 | |
| | 132 | 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. |
| | 133 | || '''`created=2007-01-01..2008-01-01`''' || query tickets created in 2007 || |
| | 134 | || '''`created=lastmonth..thismonth`''' || query tickets created during the previous month || |
| | 135 | || '''`modified=1weekago..`''' || query tickets that have been modified in the last week || |
| | 136 | || '''`modified=..30daysago`''' || query tickets that have been inactive for the last 30 days || |
