Edgewall Software

This page documents the 0.12 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 filter will display tickets relevant to you:

  • If logged in then all open tickets it will display open tickets assigned to you.
  • If not logged in but you have specified a name or email address in the preferences then it will display all open tickets where your email (or name if email not defined) is in the CC list.
  • If not logged and no name/email defined in the preferences then all open issues are displayed.

Current filters can be removed by clicking the button to the left with the minus sign on the label. New filters are added from the pulldown lists at the bottom corners of the filters box ('And' conditions on the left, 'Or' conditions on the right). 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

Trac allows you to save the query as a named query accessible from the reports module. To save a query ensure that you have Updated the view and then click the Save query button displayed beneath the results. You can also save references to queries in Wiki content, as described below.

Note: one way to easily build queries like the ones below, you can build and test the queries in the Custom report module and when ready - click Save query. This will build the query string for you. All you need to do is remove the extra line breaks.

Note: you must have the REPORT_CREATE permission in order to save queries to the list of default reports. The Save query button will only appear if you are logged in as a user that has been granted this permission. If your account does not have permission to create reports, you can still use the methods below to save a query.

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. This also allows displaying the link and description of a single ticket:


This is displayed as:

No SQL error display

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, use 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 10940)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#13112 fixed repository sync with large Subversion repository has memory leaks Jun Omae Jun Omae

I got that repository sync command with large Subversion repository eats huge memory in production environment.

  • Subversion 1.9.7
  • 14 GB
  • 48,665 revision records, 394,921 node_change records
  • Memory usage: 9 GB+

Investigating tracopt.versioncontrol.svn, I noticed repos.RevisionChangeCollector has a memory leak. According to comments of the collector, it is deprecated and ChangeCollector should be used. Using repos.ChangeCollector would reduce the memory usage, but other memory leaks still exist….

  • tracopt/versioncontrol/svn/svn_fs.py

    diff --git a/tracopt/versioncontrol/svn/svn_fs.py b/tracopt/versioncontrol/svn/svn_fs.py
    index ff82045fb..13cbc1021 100644
    a b class SubversionChangeset(Changeset):  
    10171017        pool = Pool(self.pool)
    10181018        tmp = Pool(pool)
    10191019        root = fs.revision_root(self.fs_ptr, self.rev, pool())
    1020         editor = repos.RevisionChangeCollector(self.fs_ptr, self.rev, pool())
     1020        try:
     1021            editor = repos.ChangeCollector(self.fs_ptr, root, pool())
     1022        except AttributeError:
     1023            editor = repos.RevisionChangeCollector(self.fs_ptr, self.rev,
     1024                                                   pool())
    10211025        e_ptr, e_baton = delta.make_editor(editor, pool())
    10221026        repos.svn_repos_replay(root, e_ptr, e_baton, pool())

RSS of repository sync on Trac 1.0-stable with mirror of svn.edgewall.org/repos/trac:

Rev RSS (before patch) RSS (after patch) after/before
1 62,726,144 62,713,856 99.98%
1000 101,126,144 84,533,248 83.59%
2000 128,217,088 95,047,680 74.13%
3000 160,608,256 110,559,232 68.84%
4000 191,225,856 124,428,288 65.07%
5000 218,836,992 134,868,992 61.63%
6000 247,250,944 146,202,624 59.13%
7000 277,291,008 159,305,728 57.45%
8000 305,885,184 170,926,080 55.88%
9000 332,189,696 180,367,360 54.30%
10000 356,847,616 188,334,080 52.78%
11000 382,246,912 196,726,784 51.47%
12000 409,014,272 206,376,960 50.46%
13000 434,835,456 215,494,656 49.56%
14000 459,898,880 223,096,832 48.51%
15000 485,351,424 231,702,528 47.74%
16000 512,176,128 241,451,008 47.14%
16827 534,540,288 249,696,256 46.71%

Memory profile (before the patch)

   191    509.6 MiB      1.4 MiB                       cset = self.repos.get_changeset(next_youngest)
   192    509.6 MiB      0.0 MiB                       try:
   193                                                     # steps 1. and 2.
   194    509.6 MiB    384.9 MiB                           self._insert_changeset(db, next_youngest, cset)
   195                                                 except Exception, e: # *another* 1.1. resync attempt won
   196                                                     if isinstance(e, self.env.db_exc.IntegrityError):
   197                                                         self.log.warning("Revision %s in '%s' already "
   198                                                                          "cached: %r", next_youngest,
   199                                                                          _norm_reponame(self), e)

Memory profile (after the patch)

   191    238.3 MiB      3.4 MiB                       cset = self.repos.get_changeset(next_youngest)
   192    238.3 MiB      0.0 MiB                       try:
   193                                                     # steps 1. and 2.
   194    238.3 MiB    121.6 MiB                           self._insert_changeset(db, next_youngest, cset)
   195                                                 except Exception, e: # *another* 1.1. resync attempt won
   196                                                     if isinstance(e, self.env.db_exc.IntegrityError):
   197                                                         self.log.warning("Revision %s in '%s' already "
   198                                                                          "cached: %r", next_youngest,
   199                                                                          _norm_reponame(self), e)
#13107 duplicate Changing the url when the request has not been completed causes an error in mod_wsgi - broken pipe. nwo

I noticed that there is a problem with mod_wsgi on Apache Debian 9. When I click on changeset to some large commit of my svn repo and without waiting for the resulting page to appear, I click on some other link. This action generates an error that saves me to the logs:

Traceback (most recent call last):, referer: http://my_url/trac/myrepo/changeset/1865/myrepo/trunk
  File "/home/trac/www/html/trac/cgi-bin/trac.wsgi", line 31, in application, referer: http://my_url/trac/myrepo/changeset/1865/myrepo/trunk
    return dispatch_request(environ, start_request), referer: http://my_url/trac/myrepo/changeset/1865/myrepo/trunk
  File "/usr/lib/python2.7/dist-packages/trac/web/main.py", line 581, in dispatch_request, referer: http://my_url/trac/myrepo/changeset/1865/myrepo/trunk
    return _dispatch_request(req, env, env_error), referer: http://my_url/trac/myrepo/changeset/1865/myrepo/trunk
  File "/usr/lib/python2.7/dist-packages/trac/web/main.py", line 620, in _dispatch_request, referer: http://my_url/trac/myrepo/changeset/1865/myrepo/trunk
    send_internal_error(env, req, sys.exc_info()), referer: http://my_url/trac/myrepo/changeset/1865/myrepo/trunk
  File "/usr/lib/python2.7/dist-packages/trac/web/main.py", line 751, in send_internal_error, referer: http://my_url/trac/myrepo/changeset/1865/myrepo/trunk
    req.send_error(exc_info, status=500, env=env, data=data), referer: http://my_url/trac/myrepo/changeset/1865/myrepo/trunk
  File "/usr/lib/python2.7/dist-packages/trac/web/api.py", line 732, in send_error, referer: http://my_url/trac/myrepo/changeset/1865/myrepo/trunk
    exc_info), referer: http://my_url/trac/myrepo/changeset/1865/myrepo/trunk
  File "/usr/lib/python2.7/dist-packages/trac/web/main.py", line 613, in _dispatch_request, referer: http://my_url/trac/myrepo/changeset/1865/myrepo/trunk
    dispatcher.dispatch(req), referer: http://my_url/trac/myrepo/changeset/1865/myrepo/trunk
  File "/usr/lib/python2.7/dist-packages/trac/web/main.py", line 274, in dispatch, referer: http://my_url/trac/myrepo/changeset/1865/myrepo/trunk
    req.send(output, content_type or 'text/html'), referer: http://my_url/trac/myrepo/changeset/1865/myrepo/trunk
  File "/usr/lib/python2.7/dist-packages/trac/web/api.py", line 693, in send, referer: http://my_url/trac/myrepo/changeset/1865/myrepo/trunk
    self.write(content), referer: http://my_url/trac/myrepo/changeset/1865/myrepo/trunk
  File "/usr/lib/python2.7/dist-packages/trac/web/api.py", line 833, in write, referer: http://my_url/trac/myrepo/changeset/1865/myrepo/trunk
    self._write(''.join(buf)), referer: http://my_url/trac/myrepo/changeset/1865/myrepo/trunk
IOError: Apache/mod_wsgi failed to write response data: Broken pipe, referer: http://my_url/trac/myrepo/changeset/1865/myrepo/trunkrunk

Probably trac tries to answer the original request while I have already moved to the next page and there is no one to answer. I can of course ignore such errors in the log but I do not know if this is the proper operation of the application.

#13106 duplicate OperationalError: (1052, "Column 'id' in where clause is ambiguous") hambardzum

While doing a GET operation on /query, Trac issued an internal error.

Request parameters:

{u'col': ['id',
 u'group': u'component',
 u'order': u'priority',
 u'report': u'7',
 u'status': [u'accepted', u'assigned', u'new', u'reopened']}

User agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:63.0) Gecko/20100101 Firefox/63.0

System Information

Trac 1.2.3
Babel 0.9.6
Genshi 0.7 (with speedups)
mod_wsgi 3.4 (WSGIProcessGroup WSGIApplicationGroup trac-new.instigate.local|/instigate)
MySQL server: "5.6.42", client: "5.6.42", thread-safe: 1
MySQLdb 1.2.5
Python 2.7.5 (default, Jul 13 2018, 13:06:57)
[GCC 4.8.5 20150623 (Red Hat 4.8.5-28)]
setuptools 0.9.8
Subversion 1.7.14 (r1542130)
jQuery 1.11.3
jQuery UI 1.11.4
jQuery Timepicker 1.5.5

Enabled Plugins

AllAttachmentsMacro 0.2
DefaultCc 0.4dev
mail2trac 1.0
TicketValidator 0.2dev
TracAccountManager 0.4.4
TracAutocompleteUsersPlugin 0.4.4dev
TracAwesomeAttachments 0.4dev
TracCustomFieldAdmin 0.2.13
TracEstimationTools 0.5.0dev
TracIniAdmin 0.4
TracStats 0.6.1
TracSubTicketsPlugin 0.5.4dev
TracTicketTemplate 1.0dev

Interface Customization

site-htdocs Old_instigatedesign.png, fetchmail, ins.png, instigate.png, instigatedesign.png, old_instigatedesign.png, site.js, style.css, theme.css
site-templates site.html

Python Traceback

Traceback (most recent call last):
  File "build/bdist.linux-x86_64/egg/trac/web/main.py", line 647, in _dispatch_request
  File "build/bdist.linux-x86_64/egg/trac/web/main.py", line 248, in dispatch
    resp = chosen_handler.process_request(req)
  File "build/bdist.linux-x86_64/egg/trac/ticket/query.py", line 1016, in process_request
    return self.display_html(req, query)
  File "build/bdist.linux-x86_64/egg/trac/ticket/query.py", line 1122, in display_html
    tickets = query.execute(req, cached_ids=orig_list)
  File "build/bdist.linux-x86_64/egg/trac/ticket/query.py", line 303, in execute
    self.num_items = self._count(sql, args)
  File "build/bdist.linux-x86_64/egg/trac/ticket/query.py", line 284, in _count
    % sql, args)[0][0]
  File "build/bdist.linux-x86_64/egg/trac/db/api.py", line 122, in execute
    return db.execute(query, params)
  File "build/bdist.linux-x86_64/egg/trac/db/util.py", line 128, in execute
    cursor.execute(query, params if params is not None else [])
  File "build/bdist.linux-x86_64/egg/trac/db/util.py", line 72, in execute
    return self.cursor.execute(sql_escape_percent(sql), args)
  File "/usr/lib64/python2.7/site-packages/MySQLdb/cursors.py", line 205, in execute
    self.errorhandler(self, exc, value)
  File "/usr/lib64/python2.7/site-packages/MySQLdb/connections.py", line 36, in defaulterrorhandler
    raise errorclass, errorvalue
OperationalError: (1052, "Column 'id' in where clause is ambiguous")
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. To include a literal & or | in a value, escape the character with a backslash (\).

The available operators are:

= the field content exactly matches 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

The date fields created and modified can be constrained by using the = operator and specifying a value containing two dates separated by two dots (..). Either end of the date range can be left empty, meaning that the corresponding end of the range is open. The date parser understands a few natural date specifications like "3 weeks ago", "last month" and "now", as well as Bugzilla-style date specifications like "1d", "2w", "3m" or "4y" for 1 day, 2 weeks, 3 months and 4 years, respectively. Spaces in date specifications can be left out to avoid having to quote the query string.

created=2007-01-01..2008-01-01 query tickets created in 2007
created=lastmonth..thismonth query tickets created during the previous month
modified=1weekago.. query tickets that have been modified in the last week
modified=..30daysago query tickets that have been inactive for the last 30 days

See also: TracTickets, TracReports, TracGuide

Last modified 4 years ago Last modified on Nov 3, 2014, 3:40:46 AM
Note: See TracWiki for help on using the wiki.