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.


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.



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:


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:


This is displayed as:

Results (1 - 3 of 22)

Ticket Resolution Summary Owner Reporter
#40 fixed Broken libgdal1h_1.10.0-1~precise1 package for "precise" jlarouche@… strk
#39 invalid postgresql-9.1-postgis and gdal-bin conflict jlarouche@… strk
#36 fixed please readd projects.h to libproj-dev jlarouche@… johanvdw

Full rows

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


This is displayed as:

Results (1 - 3 of 22)

Ticket Resolution Summary Owner Reporter
#40 fixed Broken libgdal1h_1.10.0-1~precise1 package for "precise" jlarouche@… strk

Reported by strk, 4 months ago.


depends on libspatialite5, but no such candidate exists in precise See and

#39 invalid postgresql-9.1-postgis and gdal-bin conflict jlarouche@… strk

Reported by strk, 5 months ago.


the gdal-bin package requires postgresql-9.1-postgis-scripts which installs topology.control file as done by postgresql-9.1-postgis.

As a result installing those two packages fails. See


$ sudo apt-get install -q postgresql-9.1-postgis gdal-bin

Reading package lists...

Building dependency tree...

Reading state information...

Suggested packages:


The following NEW packages will be installed:

gdal-bin postgresql-9.1-postgis

0 upgraded, 2 newly installed, 0 to remove and 17 not upgraded.

Need to get 3,788 kB of archives.

After this operation, 23.5 MB of additional disk space will be used.

Get:1 precise/main postgresql-9.1-postgis amd64 2.0.1-2~precise3 [3,456 kB]

Get:2 precise/main gdal-bin amd64 1.9.2-2~precise4 [332 kB]

Fetched 3,788 kB in 1s (2,855 kB/s)

Selecting previously unselected package postgresql-9.1-postgis.

(Reading database ... 69524 files and directories currently installed.)

Unpacking postgresql-9.1-postgis (from .../postgresql-9.1-postgis_2.0.1-2~precise3_amd64.deb) ...

dpkg: error processing /var/cache/apt/archives/postgresql-9.1-postgis_2.0.1-2~precise3_amd64.deb (--unpack):

trying to overwrite '/usr/share/postgresql/9.1/extension/postgis_topology.control', which is also in package postgresql-9.1-postgis-scripts 2.1.0-4.pgdg12.4+1

Actually I'm not sure who installed postgresql-9.1-postgis-scripts...

#36 fixed please readd projects.h to libproj-dev jlarouche@… johanvdw

Reported by johanvdw, 7 months ago.


The file projects.h is needed by (among others) saga gis.

See discussion at:

I'd propose to add the file at least until the new versions of the projects in ubuntugis (in this case saga) have a workaround.

I can update this myself if nobody objects.

debdiff for precise:

diff -Nru proj-4.8.0/debian/changelog proj-4.8.0/debian/changelog
--- proj-4.8.0/debian/changelog	2012-11-29 23:30:49.000000000 +0100
+++ proj-4.8.0/debian/changelog	2013-09-10 19:52:26.000000000 +0200
@@ -1,3 +1,9 @@
+proj (4.8.0-3~precise3) precise; urgency=low
+  * Add projects.h to libproj-dev.install again
+ -- Johan Van de Wauw <>  Tue, 10 Sep 2013 19:51:46 +0200
 proj (4.8.0-3~precise2) precise; urgency=medium
   * Launchpad build for Precise
diff -Nru proj-4.8.0/debian/libproj-dev.install proj-4.8.0/debian/libproj-dev.install
--- proj-4.8.0/debian/libproj-dev.install	2012-11-29 23:27:43.000000000 +0100
+++ proj-4.8.0/debian/libproj-dev.install	2013-09-10 19:51:41.000000000 +0200
@@ -3,3 +3,4 @@

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