Changes between Version 1 and Version 2 of TracQuery


Ignore:
Timestamp:
Jul 17, 2008 10:45:00 AM (12 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracQuery

    v1 v2  
    77 
    88== Filters == 
    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. 
     9When 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. 
    1610 
    1711You 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. 
     
    2216Clicking 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.   
    2317 
    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.  
     18You 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 was 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.  
    2519 
    2620The query results can be refreshed and cleared of these status indicators by clicking the ''Update'' button again. 
     
    2822== Saving Queries == 
    2923 
    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  
     24While 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. 
    3725 
    3826=== Using TracLinks === 
     
    4129{{{ 
    4230[query:status=new|assigned|reopened&version=1.0 Active tickets against 1.0] 
     31 
    4332}}} 
    4433 
     
    5140{{{ 
    5241[query:?status=new&status=assigned&status=reopened&group=owner Assigned tickets by owner] 
     42 
    5343}}} 
    5444 
     
    5848=== Using the `[[TicketQuery]]` Macro === 
    5949 
    60 The [trac:TicketQuery TicketQuery] macro lets you display lists of tickets matching certain criteria anywhere you can use WikiFormatting. 
     50The TicketQuery macro lets you display lists of tickets matching certain criteria anywhere you can use WikiFormatting. 
    6151 
    6252Example: 
     
    6858  [[TicketQuery(version=0.6|0.7&resolution=duplicate)]] 
    6959 
    70 Just like the [wiki:TracQuery#UsingTracLinks query: wiki links], the parameter of this macro expects a query string formatted according to the rules of the simple [wiki:TracQuery#QueryLanguage ticket query language]. This also allows displaying the link and description of a single ticket: 
    71 {{{ 
    72 [[TicketQuery(id=123)]] 
    73 }}} 
    74  
    75 This is displayed as: 
    76   [[TicketQuery(id=123)]] 
     60Just like the [wiki:TracQuery#UsingTracLinks query: wiki links], the parameter of this macro expects a query string formatted according to the rules of the simple [wiki:TracQuery#QueryLanguage ticket query language]. 
    7761 
    7862A more compact representation without the ticket summaries is also available: 
    7963{{{ 
    8064[[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]] 
     65 
    8166}}} 
    8267 
     
    8469  [[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]] 
    8570 
    86 Finally, if you wish to receive only the number of defects that match the query, use the ``count`` parameter. 
     71Finally if you wish to receive only the number of defects that match the query using the ``count`` parameter. 
    8772 
    8873{{{ 
    8974[[TicketQuery(version=0.6|0.7&resolution=duplicate, count)]] 
     75 
    9076}}} 
    9177 
     
    9379  [[TicketQuery(version=0.6|0.7&resolution=duplicate, count)]] 
    9480 
    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  
    11581 
    11682=== Query Language === 
    11783 
    118 `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 (`\`). 
     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. 
    11985 
    12086The available operators are: 
    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 || 
     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 || 
    12591 
    12692All of these operators can also be negated: 
    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 || 
     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 || 
    13797 
    13898----