WordPress.org

Make WordPress Core

Changes between Version 2 and Version 3 of TracQuery


Ignore:
Timestamp:
10/08/06 01:36:54 (8 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracQuery

    v2 v3  
    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 critera 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=new|assigned|reopened&version=0.8 Active tickets against 0.8] 
     30[query:status=new|assigned|reopened&version=1.0 Active tickets against 1.0] 
    2931}}} 
    3032 
    3133Which is displayed as: 
    32   [query:status=new|assigned|reopened&version=0.8 Active tickets against 0.8] 
     34  [query:status=new|assigned|reopened&version=1.0 Active tickets against 1.0] 
    3335 
    3436This uses a very simple query language to specify the criteria (see [wiki:TracQuery#QueryLanguage Query Language]). 
     
    3941}}} 
    4042 
    41 Whis is displayed as: 
     43Which is displayed as: 
    4244  [query:?status=new&status=assigned&status=reopened&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. 
    4545 
    4646=== Using the `[[TicketQuery]]` Macro === 
     
    5050Example: 
    5151{{{ 
    52 [[TicketQuery(version=0.9b1|0.9b2&resolution=duplicate)]] 
     52[[TicketQuery(version=1.0|2.0&resolution=duplicate)]] 
    5353}}} 
    5454 
    5555This is displayed as: 
    56   [[TicketQuery(version=0.9b1|0.9b2&resolution=duplicate)]] 
     56  [[TicketQuery(version=1.0|2.0&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=1.0|2.0&resolution=duplicate, compact)]] 
    6363}}} 
    6464 
    6565This is displayed as: 
    66   [[TicketQuery(version=0.9b1|0.9b2&resolution=duplicate, compact)]] 
     66  [[TicketQuery(version=1.0|2.0&resolution=duplicate, compact)]] 
    6767 
    6868=== Query Language ===