Changes between Version 2 and Version 3 of Trac Query


Ignore:
Timestamp:
Feb 3, 2015, 5:53:07 PM (10 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Trac Query

    v2 v3  
    22[[TracGuideToc]]
    33
    4 In addition to [wiki:TracReports reports], Trac provides support for ''custom ticket queries'', used to display lists of tickets meeting a specified set of criteria.
     4In addition to [wiki:TracReports reports], Trac provides support for ''custom ticket queries'', which can be used to display tickets that meet specified criteria.
    55
    66To configure and execute a custom query, switch to the ''View Tickets'' module from the navigation bar, and select the ''Custom Query'' link.
    … …  
    88== Filters ==
    99
    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.
     10When 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 in and no name/email is defined in the preferences, then all open issues are displayed.
    1414
    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.
     15Current 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'' on the criteria.
    1616
    1717You 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.
    1818
    19 Once you've edited your filters click the ''Update'' button to refresh your results.
     19After you have edited your filters, click the ''Update'' button to refresh your results.
    2020
    2121== Navigating Tickets ==
    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. 
     22Clicking 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. 
    2323
    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.
     24You 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.
    2525
    2626The query results can be refreshed and cleared of these status indicators by clicking the ''Update'' button again.
    … …  
    3535''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.
    3636
    37 
    3837=== Using TracLinks ===
    3938
    40 You may want to save some queries so that you can come back to them later.  You can do this by making a link to the query from any Wiki page.
     39You may want to save some queries so that you can come back to them later. You can do this by making a link to the query from any Wiki page.
    4140{{{
    4241[query:status=new|assigned|reopened&version=1.0 Active tickets against 1.0]
    … …  
    4645  [query:status=new|assigned|reopened&version=1.0 Active tickets against 1.0]
    4746
    48 This uses a very simple query language to specify the criteria (see [wiki:TracQuery#QueryLanguage Query Language]).
     47This uses a very simple query language to specify the criteria, see [wiki:TracQuery#QueryLanguage Query Language].
    4948
    5049Alternatively, you can copy the query string of a query and paste that into the Wiki link, including the leading `?` character:
    … …  
    6867  [[TicketQuery(version=0.6|0.7&resolution=duplicate)]]
    6968
    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:
     69Just 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 displays the link and description of a single ticket:
    7170{{{
    7271[[TicketQuery(id=123)]]
    … …  
    7675  [[TicketQuery(id=123)]]
    7776
    78 A more compact representation without the ticket summaries is also available:
     77A more compact representation without the ticket summaries is:
    7978{{{
    8079[[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]]
    … …  
    8483  [[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]]
    8584
    86 Finally, if you wish to receive only the number of defects that match the query, use the `count` parameter.
    87 
     85Finally, if you wish to receive only the number of defects that match the query, use the `count` parameter:
    8886{{{
    8987[[TicketQuery(version=0.6|0.7&resolution=duplicate, count)]]
    … …  
    9492
    9593=== 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 
     94You 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 in by placing pipes (`|`) between the columns:
    9895{{{
    9996[[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter)]]
    … …  
    104101
    105102==== Full rows ====
    106 In ''table'' format you can also have full rows by using ''rows=<field>'' like below:
    107 
     103In ''table'' format you can also have full rows by using ''rows=<field>'':
    108104{{{
    109105[[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter,rows=description)]]
    … …  
    113109[[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter,rows=description)]]
    114110
    115 
    116111=== Query Language ===
    117112
    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 (`\`).
     113`query:` TracLinks and the `[[TicketQuery]]` macro both use a mini “query language” for specifying query filters. Filters are separated by ampersands (`&`). Each filter 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 (`\`).
    119114
    120115The available operators are:
    … …  
    130125|| '''`!$=`''' || the field content does not end with any of the values ||
    131126
    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.
     127The 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 omitted to avoid having to quote the query string.
    133128|| '''`created=2007-01-01..2008-01-01`''' || query tickets created in 2007 ||
    134129|| '''`created=lastmonth..thismonth`''' || query tickets created during the previous month ||