Version 2 (modified by trac, 13 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.


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:

Change Language, Country and Keyboard-Layout at first boot
All files should be owned by root, and writable by all
Nice boot screen with Language option
livedvd: update pgrouting script
Marble: Wikipedia links need disambiguation
geomajas: slightly longer startup delay needed
regression test
52N SOS doesn't have a stop icon
docs: the sponsor pages are different between the different translations
Geomajas fails to startup
proposal for english documentation improvements
saga_gui.desktop is empty
pgRouting fails to load correctly
translate navigation bar
Remove privative libraries from Kosmo Desktop package
AtlasStyler : expired key in's deb repo
qgis: sphinx tutorial build fails
uDig: crash when you click on the 'web' tab
Tilemill boot error message
Improve Leaflet Quickstart
review jupyter file
QGis 2.18 Plugins Broken
R version 0.7 demo
o13 docs broken links
Iris packaging review for focal
Jupyter Notebook R example

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

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

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#2401 fixed ETF not deployed due to ETS download not present osgeolive@… jenriquesoriano
#2400 fixed deegree stop script not updated to 3.4.32 osgeolive@… kalxas
#2399 fixed MapServer doc page not found osgeolive@… sanak
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:


This is displayed as:

Results (1 - 3 of 1056)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#2401 fixed ETF not deployed due to ETS download not present osgeolive@… jenriquesoriano

Dear OSGeoLive team,

thanks for your efforts and congratulations for your excellent work.

We are reporting an issue in the ETF installation due to it is deployed but not loading some information needed.

We have tested the ETF deployment in the RC1. We have noticed that, the ETSs are not in the corresponding folder (/home/user/.etf/projects/inspire-ets-repository/). They should be downloaded and executed in the first deployment. We have checked the installation script and it seems correct, as we have ran it manually on the machine RC1 and the ETSs have been downloaded and the ETF is deployed properly.

Thus, it seems that there can be something in the virtual machine generation that has prevented the installation script from running completely. Probably in one of these lines of the installation scripts (/home/user/gisvm/bin/

if [ ! -d "$ETF_FOLDER/projects/inspire-ets-repository/ets-repository-osgeolive-15" ];then
	sudo mkdir "$ETF_FOLDER/projects/inspire-ets-repository/"
	cd "$ETF_FOLDER/projects/inspire-ets-repository/"
	sudo unzip -o "$TMP/"

Is there any hint that you can provide us with in order to get the installation script properly executed in the VM building process?

Thanks a lot.

#2400 fixed deegree stop script not updated to 3.4.32 osgeolive@… kalxas

#2399 fixed MapServer doc page not found osgeolive@… sanak

When starting MapServer, Firefox's 2nd tab (http://localhost/mapserver/doc) returns 404 Not Found.

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

Note: See TracWiki for help on using the wiki.