Changes between Version 1 and Version 2 of TracQuery


Ignore:
Timestamp:
2008-08-08T23:13:15Z (16 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TracQuery

    v1 v2  
    1616Clicking 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. 
    1717
    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 you edited will be displayed with italicized text.  If one of the tickets was edited such that it no longer matches the query criteria the text will also be greyed.  The query results can be refreshed and cleared of these status indicators by clicking the ''Update'' button again.
     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.
     19
     20The query results can be refreshed and cleared of these status indicators by clicking the ''Update'' button again.
    1921
    2022== Saving Queries ==
    … …  
    2628You 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.
    2729{{{
    28 [query:status!=closed&version=0.8 Active tickets against 0.8]
     30[query:status=new|assigned|reopened&version=1.0 Active tickets against 1.0]
     31
    2932}}}
    3033
    3134Which is displayed as:
    32   [query:status!=closed&version=0.8 Active tickets against 0.8]
     35  [query:status=new|assigned|reopened&version=1.0 Active tickets against 1.0]
    3336
    3437This uses a very simple query language to specify the criteria (see [wiki:TracQuery#QueryLanguage Query Language]).
    … …  
    3639Alternatively, you can copy the query string of a query and paste that into the Wiki link, including the leading `?` character:
    3740{{{
    38 [query:?status=assigned&group=owner Assigned tickets by owner]
     41[query:?status=new&status=assigned&status=reopened&group=owner Assigned tickets by owner]
     42
    3943}}}
    4044
    41 Whis is displayed as:
    42   [query:?status=assigned&group=owner Assigned tickets by owner]
    43 
    44 The advantage of this approach is that you can also specify the grouping and ordering, which is not possible using the first syntax.
     45Which is displayed as:
     46  [query:?status=new&status=assigned&status=reopened&group=owner Assigned tickets by owner]
    4547
    4648=== Using the `[[TicketQuery]]` Macro ===
    4749
    48 The `[[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.
    4951
    5052Example:
    5153{{{
    52 [[TicketQuery(version=0.9b1|0.9b2&resolution=duplicate)]]
     54[[TicketQuery(version=0.6|0.7&resolution=duplicate)]]
    5355}}}
    5456
    5557This is displayed as:
    56   [[TicketQuery(version=0.9b1|0.9b2&resolution=duplicate)]]
     58  [[TicketQuery(version=0.6|0.7&resolution=duplicate)]]
    5759
    5860Just 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].
    … …  
    6062A more compact representation without the ticket summaries is also available:
    6163{{{
    62 [[TicketQuery(version=0.9b1|0.9b2&resolution=duplicate, compact)]]
     64[[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]]
     65
    6366}}}
    6467
    6568This is displayed as:
    66   [[TicketQuery(version=0.9b1|0.9b2&resolution=duplicate, compact)]]
     69  [[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]]
     70
     71Finally if you wish to receive only the number of defects that match the query using the ``count`` parameter.
     72
     73{{{
     74[[TicketQuery(version=0.6|0.7&resolution=duplicate, count)]]
     75
     76}}}
     77
     78This is displayed as:
     79  [[TicketQuery(version=0.6|0.7&resolution=duplicate, count)]]
     80
    6781
    6882=== Query Language ===
    6983
    70 `query:` TracLinks and the `[[TicketQuery]]` macro both use a mini “query language” for specifying query filters. Basically, the filters are separate 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.
     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.
    7185
    7286The available operators are: