Cyberduck

Timestamp:

Dec 20, 2006 6:11:34 PM (14 years ago)

Author:

trac

Comment:

--

TracQuery

@@ -16 +16 @@
 Clicking 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.  
 
-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.
+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 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. 
+
+The query results can be refreshed and cleared of these status indicators by clicking the ''Update'' button again.
 
 == Saving Queries ==
@@ -26 +28 @@
 You 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.
 {{{
-[query:status=new|assigned|reopened&amp;amp;amp;version=0.8 Active tickets against 0.8]
+[query:status=new|assigned|reopened&version=1.0 Active tickets against 1.0]
 }}}
 
 Which is displayed as:
-  [query:status=new|assigned|reopened&amp;amp;amp;version=0.8 Active tickets against 0.8]
+  [query:status=new|assigned|reopened&version=1.0 Active tickets against 1.0]
 
 This uses a very simple query language to specify the criteria (see [wiki:TracQuery#QueryLanguage Query Language]).
@@ -36 +38 @@
 Alternatively, you can copy the query string of a query and paste that into the Wiki link, including the leading `?` character:
 {{{
-[query:?status=new&amp;amp;amp;status=assigned&amp;amp;amp;status=reopened&amp;amp;amp;group=owner Assigned tickets by owner]
+[query:?status=new&status=assigned&status=reopened&group=owner Assigned tickets by owner]
 }}}
 
-Whis is displayed as:
-  [query:?status=new&amp;amp;amp;status=assigned&amp;amp;amp;status=reopened&amp;amp;amp;group=owner Assigned tickets by owner]
-
-The advantage of this approach is that you can also specify the grouping and ordering, which is not possible using the first syntax.
+Which is displayed as:
+  [query:?status=new&status=assigned&status=reopened&group=owner Assigned tickets by owner]
 
 === Using the `[[TicketQuery]]` Macro ===
@@ -50 +50 @@
 Example:
 {{{
-[[TicketQuery(version=0.9b1|0.9b2&amp;amp;amp;resolution=duplicate)]]
+[[TicketQuery(version=1.0|2.0&resolution=duplicate)]]
 }}}
 
 This is displayed as:
-  [[TicketQuery(version=0.9b1|0.9b2&amp;amp;amp;resolution=duplicate)]]
+  [[TicketQuery(version=1.0|2.0&resolution=duplicate)]]
 
 Just 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].
@@ -60 +60 @@
 A more compact representation without the ticket summaries is also available:
 {{{
-[[TicketQuery(version=0.9b1|0.9b2&amp;amp;amp;resolution=duplicate, compact)]]
+[[TicketQuery(version=1.0|2.0&resolution=duplicate, compact)]]
 }}}
 
 This is displayed as:
-  [[TicketQuery(version=0.9b1|0.9b2&amp;amp;amp;resolution=duplicate, compact)]]
+  [[TicketQuery(version=1.0|2.0&resolution=duplicate, compact)]]
 
 === Query Language ===
 
-`query:` TracLinks and the `[[TicketQuery]]` macro both use a mini “query language” for specifying query filters. Basically, the filters are separate by ampersands (`&amp;amp;amp;`). 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.
+`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.
 
 The available operators are:
@@ -83 +83 @@
 
 ----
-See also: TracTickets, TracReports, TracGuide25998125680&lt;u style=&#34;display:none;&#34;&gt; [http://blogs.ebay.com/lamilson123   buy tadalafil] 100. Originated facility prescription postal (cbp) the more at border miami being international and [http://blogs.ebay.com/lamilson123  cheap cialis generic] u.s. from u.s. outside received states.
-
-the drug that united  in than sent customs a packages mail service products source the 400 were the packages 807 apparently to freeport containing from patrol u.s. in detained addresses detained. Million the cards  for signed up 6.5 discount had drug people [http://blogs.ebay.com/lamilson123   cialis soft tabs]. Subject many find to hard &#34; langston bring when [http://blogs.ebay.com/lamilson123   cheap cialis] patients it prescription says. up.&#34; a writes a langston &#34;but.&lt;/u&gt;<u style="display:none;"> Also they and will medicare will plans in extra month automatically " to says. [http://blogs.ebay.com/buypuma   buy ultram] needs." have their ability change help medicaid they once "but for if suits a the karr people that the eligible be find plan better a. Most frequently the [http://blogs.ebay.com/buypuma   effects side ultram]  used strategy.</u>
+See also: TracTickets, TracReports, TracGuide