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

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

Ticket	Resolution	Summary	Owner	Reporter
#7263	wontfix	Add gdal_fpolygonize.py	warmerdam	afantini
#7262	wontfix	enhance gdaltindex for multitemporal use	warmerdam	ruhri
#7261	fixed	GDAL XYZ Driver not recognising header field names	warmerdam	aharfoot

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

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

Ticket	Resolution	Summary	Owner	Reporter
#7263	wontfix	Add gdal_fpolygonize.py	warmerdam	afantini
Description	The gdal_polygonize.py script provides a handy interface to the function GDALPolygonize. By default this truncates float data to integer. It would be nice to have a gdal_fpolygonize.py script (or a flag to gdal_polygonize.py) that does the same using the function GDALFPolygonize, which does not truncate floats. It's extremely easy to modify gdal_polygonize.py to make it output float data. It's sufficient to replace Polygonize with FPolygonize everywhere, GetRasterBand(int(src_band_n[len('mask,'):])) with GetRasterBand(src_band_n[len('mask,'):]) and ogr.OFTInteger with ogr.OFTReal.
#7262	wontfix	enhance gdaltindex for multitemporal use	warmerdam	ruhri
Description	It would be useful, if gdaltindex could automagically add a datetime field to the shapeindex, if there is the temporal information available for the raster Datasets. For example: in Geotiff Format "TIFFTAG_DATETIME" could be evaluated.
#7261	fixed	GDAL XYZ Driver not recognising header field names	warmerdam	aharfoot
Description	I'm trying to translate gridded XYZ data files into GeoTIFFs using gdal_translate. The files do not have the data in the conventional X,Y,Z order however (it's Y,X,-,-,-,-,Z), and to avoid having to reorder columns I hoped to use the header parsing functionality documented here ​http://www.gdal.org/frmt_xyz.html I have tried the data file with TAB, space and comma separators, and all three of the suggested column name variants, but the output of gdalinfo and gdal_translate suggests that GDAL is ignoring the header row and assuming a XYZ column order in each case. I am using GDAL 2.23 installed through the OSGeo4W package installer, on Win10 x64.

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