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:

#433

Change Language, Country and Keyboard-Layout at first boot

#449

All files should be owned by root, and writable by all

#463

Nice boot screen with Language option

#522

livedvd: update pgrouting script

#654

Marble: Wikipedia links need disambiguation

#767

geomajas: slightly longer startup delay needed

#778

regression test

#790

52N SOS doesn't have a stop icon

#891

docs: the sponsor pages are different between the different translations

#954

Geomajas fails to startup

#986

proposal for english documentation improvements

#1069

saga_gui.desktop is empty

#1094

pgRouting fails to load correctly

#1097

translate navigation bar

#1145

Remove privative libraries from Kosmo Desktop package

#1344

AtlasStyler : expired key in geopublishing.org's deb repo

#1349

qgis: sphinx tutorial build fails

#1403

uDig: crash when you click on the 'web' tab

#1429

Tilemill boot error message

#1945

Improve Leaflet Quickstart

#2051

review jupyter file

#2111

QGis 2.18 Plugins Broken

#2134

R version 0.7 demo

#2173

o13 docs broken links

#2270

Iris packaging review for focal

#2335

Jupyter Notebook R example

#2397

Sphinx docs build fails

#2442

pgAdmin4 on VMDK v16 fails to start

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:

#433, #449, #463, #522, #654, #767, #778, #790, #891, #954, #986, #1069, #1094, #1097, #1145, #1344, #1349, #1403, #1429, #1945, #2051, #2111, #2134, #2173, #2270, #2335, #2397, #2442

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:

28

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

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

Ticket	Resolution	Summary	Owner	Reporter
#2477	fixed	Remove unused components on Weblate	osgeolive@…	cvvergara
#2476	fixed	Remove worldwindjava documentation	osgeolive@…	cvvergara
#2475	fixed	Remove viking documentation	osgeolive@…	cvvergara

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

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

Ticket	Resolution	Summary	Owner	Reporter
#2477	fixed	Remove unused components on Weblate	osgeolive@…	cvvergara
Description	Some components of retired projects still available for translation on weblate. Remove components of retired projects: mapslicer geomajas liblas 52nWSS atlasstyler cartaro geopublisher gpsdrive mapfish mapguide mapwindow tilemill tomcat webworldwind geokettle iris metacrs mb-system osgearth sahana ushahidi viking worldwindjava kosmo tinyows ncWMS 52nWPS Components suffix _overview _quickstart
#2476	fixed	Remove worldwindjava documentation	osgeolive@…	cvvergara
Description	worldwindjava was retired on v11, the documentation is not used and needs to be removed.
#2475	fixed	Remove viking documentation	osgeolive@…	cvvergara
Description	viking was retired on v11, the documentation is not used and needs to be removed.

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