Changes between Version 2 and Version 3 of TracQuery


Ignore:
Timestamp:
Apr 24, 2006, 10:33:44 AM (19 years ago)
Author:
trac
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!=closed&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!=closed&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=assigned&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=assigned&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.