Edgewall Software

Changes between Version 42 and Version 43 of TracQuery


Ignore:
Timestamp:
Jan 3, 2015, 1:33:09 PM (9 years ago)
Author:
figaro
Comment:

Cosmetic changes

Legend:

Unmodified
Added
Removed
Modified

  • TracQuery

    v42 v43  
    33[[TranslatedPages]]
    44
    5 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.
     5In addition to [wiki:TracReports reports], Trac provides support for ''custom ticket queries'', which can be used to display tickets that meet specified criteria.
    66
    77To configure and execute a custom query, switch to the ''View Tickets'' module from the navigation bar, and select the ''Custom Query'' link.
    … …  
    99== Filters ==
    1010
    11 When you first go to the query page the default filter will display tickets relevant to you:
    12  * If logged in then all open tickets it will display open tickets assigned to you.
    13  * 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.
    14  * If not logged and no name/email defined in the preferences then all open issues are displayed.
     11When you first go to the query page, the default filter will display tickets relevant to you:
     12 * If logged in then all open tickets, it will display open tickets assigned to you.
     13 * 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.
     14 * If not logged in and no name/email is defined in the preferences, then all open issues are displayed.
    1515
    16 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.
     16Current 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.
    1717
    1818You 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.
    1919
    20 Once you've edited your filters click the ''Update'' button to refresh your results.
     20After you have edited your filters, click the ''Update'' button to refresh your results.
    2121
    2222== Navigating Tickets ==
    23 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. 
     23Clicking 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. 
    2424
    25 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.
     25You 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.
    2626
    2727The query results can be refreshed and cleared of these status indicators by clicking the ''Update'' button again.
    … …  
    3636''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.
    3737
    38 
    3938=== Using TracLinks ===
    4039
    41 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.
     40You 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.
    4241{{{
    4342[query:status=new|assigned|reopened&version=1.0 Active tickets against 1.0]
    … …  
    4746  [query:status=new|assigned|reopened&version=1.0 Active tickets against 1.0]
    4847
    49 This uses a very simple query language to specify the criteria (see [wiki:TracQuery#QueryLanguage Query Language]).
     48This uses a very simple query language to specify the criteria, see [wiki:TracQuery#QueryLanguage Query Language].
    5049
    5150Alternatively, you can copy the query string of a query and paste that into the Wiki link, including the leading `?` character:
    … …  
    6968  [[TicketQuery(version=0.6|0.7&resolution=duplicate)]]
    7069
    71 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:
     70Just 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:
    7271{{{
    7372[[TicketQuery(id=123)]]
    … …  
    7776  [[TicketQuery(id=123)]]
    7877
    79 A more compact representation without the ticket summaries is also available:
     78A more compact representation without the ticket summaries is:
    8079{{{
    8180[[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]]
    … …  
    8584  [[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]]
    8685
    87 Finally, if you wish to receive only the number of defects that match the query, use the `count` parameter.
    88 
     86Finally, if you wish to receive only the number of defects that match the query, use the `count` parameter:
    8987{{{
    9088[[TicketQuery(version=0.6|0.7&resolution=duplicate, count)]]
    … …  
    9593
    9694=== Customizing the ''table'' format ===
    97 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:
    98 
     95You 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:
    9996{{{
    10097[[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter)]]
    … …  
    105102
    106103==== Full rows ====
    107 In ''table'' format you can also have full rows by using ''rows=<field>'' like below:
    108 
     104In ''table'' format you can also have full rows by using ''rows=<field>'':
    109105{{{
    110106[[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter,rows=description)]]
    … …  
    114110[[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter,rows=description)]]
    115111
    116 
    117112=== Query Language ===
    118113
    119 `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 (`\`).
     114`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 (`\`).
    120115
    121116The available operators are:
    … …  
    131126|| '''`!$=`''' || the field content does not end with any of the values ||
    132127
    133 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.
     128The 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.
    134129|| '''`created=2007-01-01..2008-01-01`''' || query tickets created in 2007 ||
    135130|| '''`created=lastmonth..thismonth`''' || query tickets created during the previous month ||