Edgewall Software

This page documents the 0.11 release. Documentation for other releases can be found here.

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:

Wiki preview injects new lines
request for colour legend (or something similar) for ticket groups in reports
Ticket Dependencies
Link to diff of specifik wiki change instead of the page itself
All ticket modifications should be tracked in timeline
Installing on Windows, drive other than C:
Diffviewer should try to convert the text into utf-8.
merging of similar tickets
Python process sometimes hangs on Windows Server 2003
IE 5-6 over HTTPS broken downloads

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:

#181, #204, #226, #239, #351, #413, #450, #475, #519, #529

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:

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

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#12998 cantfix permission add user but return 401 use htdigest cybermerlin@…
freebsd-update fetch
freebsd-update install
uname # 11.1
pkg update
pkg upgrade -f
pkg install trac
pkg install trac-mercurial
trac-admin /var/trac/proj initenv
trac-admin proj deploy /var/www/trac/proj
trac-admin proj permission add superuser TRAC_ADMIN
trac-admin proj repository add proj /var/hg/proj/.hg
trac-admin proj repository sync proj
#UnicodeDecodeError: 'ascii' codec can't decode byte 0xd0 in position 23: ordinal not in range(128)
htdigest -c /var/hg/.htdigest pipi superuser
#enter password
tracd -p 8000 -r --auth="*,/var/hg/.htdigest,pipi" -e /var/trac -r
  • go to the browser to http://trac.local:8080/proj
  • see some warn|errors
  • try login
  • see popup login\pass
  • write it
  • see now same popup
  • try write login\pass
  • …repeat…about 3rd times
  • press the button cancel
  • see 401 code
#12996 cantfix AttributeError: 'Environment' object has no attribute 'get_db_cnx' user

How to Reproduce

While doing a GET operation on /admin/accounts/users, Trac issued an internal error.

(please provide additional details here)

Request parameters:

{'cat_id': u'accounts', 'panel_id': u'users', 'path_info': None}

User agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36

System Information

Trac 1.2.2
Babel 0.9.6
Genshi 0.6 (without speedups)
GIT 2.14.1.windows.1
mod_wsgi 3.5 (WSGIProcessGroup WSGIApplicationGroup %{GLOBAL})
pysqlite 2.6.3
Python 2.7.14 (v2.7.14:84471935ed, Sep 16 2017, 20:19:30) [MSC v.1500 32 bit (Intel)]
setuptools 20.9.0
jQuery 1.11.3
jQuery UI 1.11.4
jQuery Timepicker 1.5.5

Enabled Plugins

tracusermanagerplugin 0.5.dev0

Interface Customization

Python Traceback

Traceback (most recent call last):
  File "build\bdist.win32\egg\trac\web\main.py", line 623, in _dispatch_request
  File "build\bdist.win32\egg\trac\web\main.py", line 239, in dispatch
    resp = chosen_handler.process_request(req)
  File "build\bdist.win32\egg\trac\admin\web_ui.py", line 109, in process_request
    provider.render_admin_panel(req, cat_id, panel_id, path_info)
  File "build\bdist.win32\egg\tracusermanager\admin.py", line 124, in render_admin_panel
    um_data.update(users = UserManager(self.env).get_active_users())
  File "build\bdist.win32\egg\tracusermanager\api.py", line 172, in get_active_users
    return self.search_users()
  File "build\bdist.win32\egg\tracusermanager\api.py", line 215, in search_users
    for username in self.user_store.search_users()]
  File "build\bdist.win32\egg\tracusermanager\api.py", line 321, in search_users
    db = self.env.get_db_cnx()
AttributeError: 'Environment' object has no attribute 'get_db_cnx'
#12992 cantfix git repo browser shows only comment and revisions but no files and diffs therochworks@…

Trac: 1.2.2

git: 2.16.2 and also 2.7

OS: Ubuntu xenial latest updates

If I want to browse my git repository the trac browser show only a revision and the latest commit message. It doesn't show any content (files). The same issue exists in the changeset view.

I found only the following log entry:

2018-03-11 16:01:55,228 Trac[PyGIT] DEBUG: /usr/bin/git exits with 128, dir: u'/path/to/.git', args: ls-tree ('-z', '-l', 'ba8ca6ac247', '--', ''), stderr: 'fatal: empty string is not a valid pathspec. please use . instead if you meant to match all paths\n'

Why is this a debug message and no error message?

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

Last modified 8 years ago Last modified on Apr 10, 2010, 6:37:10 PM
Note: See TracWiki for help on using the wiki.