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
Sphinx docs build fails

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

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

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#2429 fixed Base Lubuntu ISO image needs to be stored in somewhere osgeolive@… sanak
#2427 fixed Python3 azure obesity osgeolive@… darkblueb
#2424 fixed actinia install error osgeolive@… darkblueb
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 1077)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#2429 fixed Base Lubuntu ISO image needs to be stored in somewhere osgeolive@… sanak

Currently, OSGeoLive 16.0 alpha image's base seems to be Lubuntu 22.04.1,


but the Lubuntu ISO image (lubuntu-22.04.1-desktop-amd64.iso) is not downloadable from Lubuntu download site, because the site seems to drop previous patch version when new patch version (22.04.2) is released.

I think that it's better to store Lubuntu base ISO image and hash to somewhere in to be able to build ISO image, even if new patch version is released.

#2427 fixed Python3 azure obesity osgeolive@… darkblueb

the system-level python3 at /usr/lib/python3 is burdened with vendor-specific contents (see image)

#2424 fixed actinia install error osgeolive@… darkblueb
user@osgeolive:~/gisvm/bin$ sudo ./ 
Starting "" ...
Ign:1 cdrom://OSGeoLive build40-1949c1b - Release amd64 (20220809) jammy InRelease
Hit:2 cdrom://OSGeoLive build40-1949c1b - Release amd64 (20220809) jammy Release
Hit:4 jammy InRelease                                                      
Get:5 jammy-updates InRelease [119 kB]                                     
Get:6 jammy-updates/main amd64 Packages [1031 kB]
Get:7 jammy-security InRelease [110 kB]
Get:8 jammy-updates/main Translation-en [216 kB]
Get:9 jammy InRelease [23.8 kB]
Get:10 jammy-security/main amd64 Packages [764 kB]
Hit:11 jammy InRelease
Get:12 jammy-updates/main amd64 DEP-11 Metadata [102 kB]
Get:13 jammy InRelease [17.5 kB]
Get:14 jammy-updates/main amd64 c-n-f Metadata [14.1 kB]
Get:15 jammy-updates/restricted amd64 Packages [816 kB]
Get:16 jammy/main amd64 Packages [33.7 kB]
Get:17 jammy/main amd64 Packages [768 B]
Get:18 jammy-security/main Translation-en [151 kB]
Get:19 jammy-security/main amd64 DEP-11 Metadata [41.4 kB]
Get:20 jammy-security/main amd64 c-n-f Metadata [9028 B]
Get:21 jammy-security/restricted amd64 Packages [773 kB]
Get:22 jammy-updates/restricted Translation-en [128 kB]
Get:23 jammy-updates/restricted amd64 c-n-f Metadata [604 B]
Get:24 jammy-updates/universe amd64 Packages [902 kB]
Get:25 jammy-security/restricted Translation-en [121 kB]
Get:26 jammy-security/restricted amd64 c-n-f Metadata [604 B]
Get:27 jammy-security/universe amd64 Packages [718 kB]
Get:28 jammy-security/universe Translation-en [119 kB]
Get:29 jammy-security/universe amd64 DEP-11 Metadata [18.5 kB]
Get:30 jammy-security/universe amd64 c-n-f Metadata [14.2 kB]
Get:31 jammy-security/multiverse amd64 Packages [19.4 kB]
Get:32 jammy-security/multiverse amd64 c-n-f Metadata [252 B]
Get:33 jammy-updates/universe Translation-en [181 kB]
Get:34 jammy-updates/universe amd64 DEP-11 Metadata [269 kB]
Get:35 jammy-updates/universe amd64 c-n-f Metadata [18.6 kB]
Get:36 jammy-updates/multiverse amd64 Packages [24.1 kB]
Get:37 jammy-updates/multiverse amd64 DEP-11 Metadata [940 B]
Get:38 jammy-updates/multiverse amd64 c-n-f Metadata [468 B]
Fetched 6756 kB in 31s (218 kB/s)
Reading package lists...
W: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package python3-actinia-core
E: Unable to locate package python3-actinia-statistic-plugin
usage: grass [-h] [-v] [--text] [--gtext] [--gui] [-c [CRS]] [-e] [--config [CONFIG ...]] [--tmp-mapset]
             [--tmp-location CRS] [-f] [--exec ...]
grass: error: unrecognized arguments: -text
usage: grass [-h] [-v] [--text] [--gtext] [--gui] [-c [CRS]] [-e] [--config [CONFIG ...]] [--tmp-mapset]
             [--tmp-location CRS] [-f] [--exec ...]
grass: error: unrecognized arguments: -text
Downloading actinia logo ...
--2023-04-20 18:00:36--
Resolving (
Connecting to (||:443... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: [following]
--2023-04-20 18:00:36--
Reusing existing connection to
HTTP request sent, awaiting response... 404 Not Found
2023-04-20 18:00:37 ERROR 404: Not Found.

Finished ""
Disk Usage1:,Filesystem,1K-blocks,Used,Available,Use%,Mounted_on,date
Disk Usage2:,/cow,11783,415,11368,4%,/,2023-04-20 18:00:37+00:00
Temp Usage:,0        /tmp

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.