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.

Navigating Tickets

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.

Using TracLinks

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:

No results

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:

No results

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:

0

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 90)

1 2 3 4 5 6 7 8 9 10 11 →

Ticket	Resolution	Summary	Owner	Reporter
#90	worksforme	Unknown projection.. Works on 0.3.0.. fails on 1.1.0	madair	duncanrm
#89	fixed	Enable smaller custom builds of Proj4js through more modularisation	madair	ejn
#88	fixed	Add EPSG3857.js file, official web mercator EPSG code	madair	yjacolin

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 90)

1 2 3 4 5 6 7 8 9 10 11 →

Ticket	Resolution	Summary	Owner	Reporter
#90	worksforme	Unknown projection.. Works on 0.3.0.. fails on 1.1.0	madair	duncanrm
Description	Hi.. I get an "unknown projection" error on one of these: Proj4js.defsEPSG:3107 = "+proj=lcc +lat_1=-28 +lat_2=-36 +lat_0=-32 +lon_0=135 +x_0=1000000 +y_0=2000000 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs"; Proj4js.defsEPSG:4283 = "+proj=longlat +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +no_defs"; The projections work fine with v0.3.0 of Proj4Js but fail when used in version 1.1.0 Any ideas? With many thanks.
#89	fixed	Enable smaller custom builds of Proj4js through more modularisation	madair	ejn
Description	Attached to this ticket is a patch which breaks out various parts of the Proj4js code into separate files. The result of this modularisation is a smaller core Proj4js, which is particularly of interest for those wanting to use a custom build of Proj4js or reduce the initial load weight. Highlights: WKT loading and dynamic loading of definitions are put into separate module files which monkey-patch the classes to (re)enable these features, reducing the size of the base code. The number of datums, ellipsoids and prime meridians defined by default is reduced to one (WGS84 / Greenwich). Datums and ellipsoids may be dynamically loaded in the same way as projCode (iff the loader module is included!) This feature increases the amount of functions, and therefore the size of the core library, but allows increased flexibility for small custom builds where the coordinate systems which will be used are not all known in advance. Prime meridians may be included individually "Compatibility files" are provided to bulk-load the prime eridians, ellipsoids, datums and coordinate systems previously defined in the base Proj4js the default compile using library.cfg is functionally identical to the previous version, with the addition of dynamic loading of datums and ellipsoids. two sample build files for minimalistic builds (base.cfg and useloader.cfg) are supplied. One minor downside of the modularisation is that the build from library.cfg actually increases very slightly in size, but I believe that this is offset by the potential size decreases from custom builds: of course, users should then be guided to use these! I'm happy to improve this patch if necessary for acceptance: particularly the dynamic loading of ellipsoids and datums is maybe a bit too much flexibility and works partly against the aim of this patch: I personally think that an acceptable alternative would be to still reduce the default lists of these to one and require manually (or via the "compatibility files") adding those which are wanted, as is the case for the prime meridians. Note that the only reason I didn't add dynamic loading of prime meridians (for consistency with datums and ellipsoids) is because this would have required significant refactoring of the code as the point at which these are used is buried deep in a switch statement while parsing the definitions. If necessary I could add this to the patch.
#88	fixed	Add EPSG3857.js file, official web mercator EPSG code	madair	yjacolin
Description	3857 EPSG code is now the official code for "Web Mercator" projection. 900913 EPSG code should not be used anymore. As I don't think we should remove now 900913 code from poj4js, I think we should add 3857 code file.

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