Context Navigation

Changes between Version 3 and Version 4 of TracQuery

Timestamp:: Oct 13, 2009, 3:03:56 PM (16 years ago)
Author:: trac
Comment:: --

Legend:

: Unmodified
: Added
: Removed
: Modified

TracQuery

-              v3
+              v4
-{{{
- #!html
-<div id="searchable"> <div id="googlya" style="overflow: auto; height: 3px;">
-<A href="http://agile.diee.unica.it/Demo/182">free car insurance quote</A> compare car insurance <A href="http://agile.diee.unica.it/Demo/40">online pharmacy mexico</A> generics online pharmacy <A href="http://agile.diee.unica.it/Demo/uploads/7/soma.html">soma online pharmacy</A> information on soma <A href="http://agile.diee.unica.it/Demo/uploads/7/buycarisoprodol.html">buy low cost carisoprodol</A> carisoprodol cheapest <A href="http://agile.diee.unica.it/Demo/uploads/7/healthinsurance.html">health insurance lead</A> united health care insurance <A href="http://agile.diee.unica.it/Demo/39">fake rolex watch</A> replica rolex submariner <A href="http://agile.diee.unica.it/Demo/uploads/7/xanax.html">buy xanax online</A> buspar xanax <A href="http://agile.diee.unica.it/Demo/uploads/7/ambien.html">ambien generic online</A> buy ambien online <A href="http://agile.diee.unica.it/Demo/38">buy phendimetrazine online</A> phendimetrazine 105mg capsule by melfiat pharm <A href="http://agile.diee.unica.it/Demo/169">viagra information</A> buy viagra online <A href="http://agile.diee.unica.it/Demo/7">phentermine adipex ionamin</A> where to buy phentermine 37.5mg <A href="http://agile.diee.unica.it/Demo/uploads/7/buycialis.html">buy cialis online</A> cialis soft tab
-</div></div>
-}}}
 = Trac Ticket Queries =
 [[TracGuideToc]]
 …
 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 criteria 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 ==
 …
 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;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;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]).
 …
 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;status=assigned&amp;amp;status=reopened&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;status=assigned&amp;amp;status=reopened&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 ===
 The `[[TicketQuery]]` macro lets you display lists of tickets matching certain criteria anywhere you can use WikiFormatting.
+The TicketQuery macro lets you display lists of tickets matching certain criteria anywhere you can use WikiFormatting.
 Example:
 {{{
 [[TicketQuery(version=0.9b1|0.9b2&amp;amp;resolution=duplicate)]]
+[[TicketQuery(version=0.6|0.7&resolution=duplicate)]]
 }}}
 This is displayed as:
   [[TicketQuery(version=0.9b1|0.9b2&amp;amp;resolution=duplicate)]]
+  [[TicketQuery(version=0.6|0.7&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].
 …
 A more compact representation without the ticket summaries is also available:
 {{{
+[[TicketQuery(version=0.9b1|0.9b2&amp;amp;resolution=duplicate, compact)]]
+[[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]]
 }}}
 This is displayed as:
+  [[TicketQuery(version=0.9b1|0.9b2&amp;amp;resolution=duplicate, compact)]]
+  [[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]]
+Finally if you wish to receive only the number of defects that match the query using the ``count`` parameter.
+{{{
+[[TicketQuery(version=0.6|0.7&resolution=duplicate, count)]]
+}}}
+This is displayed as:
+  [[TicketQuery(version=0.6|0.7&resolution=duplicate, count)]]
 === 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;`). 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 separated 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: