wiki:TracQuery

Version 2 (modified by trac, 4 years ago) (diff)

--

Trac Ticket Queries

In addition to reports, Trac provides support for custom ticket queries, used to display lists of tickets meeting a specified set of criteria.

To configure and execute a custom query, switch to the View Tickets module from the navigation bar, and select the Custom Query link.

Filters

When you first go to the query page the default filters will display all open tickets, or if you're logged in it will display open tickets assigned to you. Current filters can be removed by clicking the button to the right with the minus sign on the label. New filters are added from the pulldown list in the bottom-right corner of the filters box. Filters with either a text box or a pulldown menu of options can be added multiple times to perform an or of the criteria.

You can use the fields just below the filters box to group the results based on a field, or display the full description for each ticket.

Once you've edited your filters click the Update button to refresh your results.

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 which were 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. 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

While Trac does not yet allow saving a named query and somehow making it available in a navigable list, you can save references to queries in Wiki content, as described below.

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&version=1.0 Active tickets against 1.0]

Which is displayed as:

Active tickets against 1.0

This uses a very simple query language to specify the criteria (see 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&status=assigned&status=reopened&group=owner Assigned tickets by owner]

Which is displayed as:

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.

Example:

[[TicketQuery(version=0.6|0.7&resolution=duplicate)]]

This is displayed as:

#42
MUD engine
#74
ATOM/RSS aggregator with GTK UI capable of handling big number of subscriptions
#1115
A Replacement for GNU Make using Haskell
#1128
Cabal + nhc98 + yhc

Just like the query: wiki links, the parameter of this macro expects a query string formatted according to the rules of the simple ticket query language.

A more compact representation without the ticket summaries is also available:

[[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]]

This is displayed as:

#42, #74, #1115, #1128

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:

4

Customizing the table format

You can also customize the columns displayed in the table format (format=table) by using col=<field> - you can specify multiple fields and what order they are displayed by placing pipes (|) between the columns like below:

[[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter)]]

This is displayed as:

Results (1 - 3 of 117)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#1624 wontfix Achat De Hydroxyzine seredobace
#1623 wontfix Achat De Clomiphene seredobace
#1615 fixed Haskell support for Visual Studio 11 and upcoming versions zhulikas
1 2 3 4 5 6 7 8 9 10 11

Full rows

In table format you can also have full rows by using rows=<field> like below:

[[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter,rows=description)]]

This is displayed as:

Results (1 - 3 of 117)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#1624 wontfix Achat De Hydroxyzine seredobace
Description

http://i.imgur.com/FHl0s.jpg hydroxyzine acheter en france atarax prix maroc hydroxyzine générique atarax 5 milligrams prix hydroxyzine for migraines atarax famille hydroxyzine otc us atarax et fatigue hydroxyzine pamoate withdrawal atarax 25 comprimé hydroxyzine 50 mg atarax allergie pollen vente hydroxyzine générique acheter atarax 25mg achat hydroxyzine atarax scanner hydroxyzine online canada atarax chez le chien hydroxyzine en ligne atarax dose létale hydroxyzine 25 mg prix atarax le vrai pas le générique hydroxyzine wiki atarax generique 10 atarax hydroxyzine atarax et femmes enceintes acheter du hydroxyzine a paris atarax for anxiety hydroxyzine opiate withdrawal prix atarax 2,5 hydroxyzine pamoate 100 mg acheter atarax avec paypal hydroxyzine achat moins cher atarax 25mg enceinte achat hydroxyzine sans ordonnance achat atarax générique pas cher en france hydroxyzine pamoate hcl atarax définition hydroxyzine overdose atarax 5mg

#1623 wontfix Achat De Clomiphene seredobace
Description

http://i.imgur.com/FHl0s.jpg clomiphene prix france clomipramine mylan 75 mg acheter du clomiphene sans ordonnance clomid ocular side effects acheter clomiphene 5mg clomid early pregnancy signs clomiphene 10mg prix traitement clomid dérèglement cycle clomiphene 20mg posologie achat clomid pas cher acheter clomiphene clomid et absence de regle prix clomiphene 5mg en pharmacie clomid nidation clomiphene 20mg canada clomid drug clomiphene veritable clomide vidal générique clomiphene france clomid poids prix clomiphene generique clomid belgique clomiphene générique 5mg clomid et acné prix clomiphene andorre clomid 20mg prix en pharmacie acheter du clomiphene en ligne clomid opk clomiphene prix officiel clomid help clomiphene 20 mg clomipramine 75 grossesse clomiphene 50 mg clomid pendant grossesse clomiphene vente en france clomipramine pronunciation achat clomiphene en ligne clomid gonadotrophine et ovulation clomiphene 10 mg prix clomid pilule

#1615 fixed Haskell support for Visual Studio 11 and upcoming versions zhulikas
Description

The idea is to take advantage of Visual Studio SDK to create Haskell language support.

Things to implement:

  • Project and file templates
  • Syntax highlighting
  • GHC support
  • Debugger support
  • Autocompletion restricting options to imported modules
  • GHCi in Visual Studio Shell
  • Underline incorrect grammar and display errors

I plan to support Visual Studio 11 which is the new VS and will be released soon. After that is done, it should not be hard to port extension to VS2010. With all that being done, Windows users will finally have a decent Haskell IDE :-)

1 2 3 4 5 6 7 8 9 10 11

Query Language

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:

= the field content exactly matches the one of the values
~= the field content contains one or more of the values
^= the field content starts with one of the values
$= the field content ends with one of the values

All of these operators can also be negated:

!= the field content matches none of the values
!~= the field content does not contain any of the values
!^= the field content does not start with any of the values
!$= the field content does not end with any of the values

See also: TracTickets, TracReports, TracGuide