Changes between Version 2 and Version 3 of TracQuery


Ignore:
Timestamp:
11/09/05 18:26:14 (19 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TracQuery

    v2 v3  
    66To configure and execute a custom query, switch to the ''View Tickets'' module from the navigation bar, and select the ''Custom Query'' link.
    77
    8 == Query Form ==
     8== Filters ==
     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.
    910
    10 A form will be presented, letting you select or enter values for any of the ticket properties (both built-in and custom). Any value selected/entered in this form will be used to constrain the set of tickets displayed. Only tickets where properties match the criteria will be displayed.
     11You 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.
    1112
    12 == Results Display ==
     13Once you've edited your filters click the ''Update'' button to refresh your results.
    1314
    14 After executing the search, a list of tickets meeting the selected criteria will show. By default, the list is sorted by priority. You can change the sorting to any other visible column by clicking on the corresponding column header. Clicking the same header again will reverse the sort order.
     15== Navigating Tickets ==
     16Clicking 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. 
    1517
    16 You can edit the query by clicking ''Refine Query''.
     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 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.
     19
     20== Saving Queries ==
     21
     22While 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.
     23
     24=== Using TracLinks ===
     25
     26You 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.
     27{{{
     28[query:status!=closed&version=0.8 Active tickets against 0.8]
     29}}}
     30
     31Which is displayed as:
     32  [query:status!=closed&version=0.8 Active tickets against 0.8]
     33
     34This uses a very simple query language to specify the criteria (see [wiki:TracQuery#QueryLanguage Query Language]).
     35
     36Alternatively, you can copy the query string of a query and paste that into the Wiki link, including the leading `?` character:
     37{{{
     38[query:?status=assigned&group=owner Assigned tickets by owner]
     39}}}
     40
     41Whis is displayed as:
     42  [query:?status=assigned&group=owner Assigned tickets by owner]
     43
     44The advantage of this approach is that you can also specify the grouping and ordering, which is not possible using the first syntax.
     45
     46=== Using the `[[TicketQuery]]` Macro ===
     47
     48The `[[TicketQuery]]` macro lets you display lists of tickets matching certain criteria anywhere you can use WikiFormatting.
     49
     50Example:
     51{{{
     52[[TicketQuery(version=0.9b1|0.9b2&resolution=duplicate)]]
     53}}}
     54
     55This is displayed as:
     56  [[TicketQuery(version=0.9b1|0.9b2&resolution=duplicate)]]
     57
     58Just 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].
     59
     60A more compact representation without the ticket summaries is also available:
     61{{{
     62[[TicketQuery(version=0.9b1|0.9b2&resolution=duplicate, compact)]]
     63}}}
     64
     65This is displayed as:
     66  [[TicketQuery(version=0.9b1|0.9b2&resolution=duplicate, compact)]]
     67
     68=== Query Language ===
     69
     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.
     71
     72The available operators are:
     73|| '''=''' || the field content exactly matches the one of the values ||
     74|| '''~=''' || the field content contains one or more of the values ||
     75|| '''!^=''' || the field content starts with one of the values ||
     76|| '''$=''' || the field content ends with one of the values ||
     77
     78All of these operators can also be negated:
     79|| '''!=''' || the field content matches none of the values ||
     80|| '''!~=''' || the field content does not contain any of the values ||
     81|| '''!!^=''' || the field content does not start with any of the values ||
     82|| '''!$=''' || the field content does not end with any of the values ||
    1783
    1884----