Cyberduck Mountain Duck CLI

Changes between Version 2 and Version 3 of TracQuery


Ignore:
Timestamp:
Oct 8, 2006 12:24:14 PM (15 years ago)
Author:
anonymous
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracQuery

    v2 v3  
    2626You 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.
    2727{{{
    28 [query:status=new|assigned|reopened&version=0.8 Active tickets against 0.8]
     28[query:status=new|assigned|reopened&version=0.8 Active tickets against 0.8]
    2929}}}
    3030
    3131Which is displayed as:
    32   [query:status=new|assigned|reopened&version=0.8 Active tickets against 0.8]
     32  [query:status=new|assigned|reopened&version=0.8 Active tickets against 0.8]
    3333
    3434This uses a very simple query language to specify the criteria (see [wiki:TracQuery#QueryLanguage Query Language]).
     
    3636Alternatively, you can copy the query string of a query and paste that into the Wiki link, including the leading `?` character:
    3737{{{
    38 [query:?status=new&status=assigned&status=reopened&group=owner Assigned tickets by owner]
     38[query:?status=new&status=assigned&status=reopened&group=owner Assigned tickets by owner]
    3939}}}
    4040
    4141Whis is displayed as:
    42   [query:?status=new&status=assigned&status=reopened&group=owner Assigned tickets by owner]
     42  [query:?status=new&status=assigned&status=reopened&group=owner Assigned tickets by owner]
    4343
    4444The advantage of this approach is that you can also specify the grouping and ordering, which is not possible using the first syntax.
     
    5050Example:
    5151{{{
    52 [[TicketQuery(version=0.9b1|0.9b2&resolution=duplicate)]]
     52[[TicketQuery(version=0.9b1|0.9b2&resolution=duplicate)]]
    5353}}}
    5454
    5555This is displayed as:
    56   [[TicketQuery(version=0.9b1|0.9b2&resolution=duplicate)]]
     56  [[TicketQuery(version=0.9b1|0.9b2&resolution=duplicate)]]
    5757
    5858Just 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].
     
    6060A more compact representation without the ticket summaries is also available:
    6161{{{
    62 [[TicketQuery(version=0.9b1|0.9b2&resolution=duplicate, compact)]]
     62[[TicketQuery(version=0.9b1|0.9b2&resolution=duplicate, compact)]]
    6363}}}
    6464
    6565This is displayed as:
    66   [[TicketQuery(version=0.9b1|0.9b2&resolution=duplicate, compact)]]
     66  [[TicketQuery(version=0.9b1|0.9b2&resolution=duplicate, compact)]]
    6767
    6868=== Query Language ===
    6969
    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.
     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.
    7171
    7272The available operators are:
     
    8383
    8484----
    85 See also: TracTickets, TracReports, TracGuide
     85See also: TracTickets, TracReports, TracGuide25998125680