Trac Ticket Queries

In addition to reports, Trac provides support for custom ticket queries, which can be used to display tickets that meet specified 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 in and no name/email is 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 on 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.

After you have 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

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 in by placing pipes (|) between the columns:


This is displayed as:

Results (1 - 3 of 5549)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#8317 fixed twisted.web doesn't correctly handle invalid header blocks. Lukasa
#8304 fixed twisted.enterprise.adbapi has a lot of simple twistedchecker errors hawkowl hawkowl
#8300 fixed Pass down write callable in t.w.template mithrandi mithrandi
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>:


This is displayed as:

Results (1 - 3 of 5549)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#8317 fixed twisted.web doesn't correctly handle invalid header blocks. Lukasa

Spotted while attempting to surgically remove pipelining from twisted.web.

A test in twisted.web.test_http (TestParsing.test_invalidHeaderNoColon) attempts to test that Twisted 400s when receiving invalid header blocks, specifically those which contain a header with no colon.

Unfortunately, that test doesn't *quite* test the correct behaviour. This is because Twisted delays header processing to allow for the possibility of header folding (deprecated as of RFC 7230). That means that Twisted only processes a header on the line *after* it is received.

That's fine if the bad header appears almost anywhere in the header block, but if it appears as the *last* header then Twisted will parse that header and then unconditionally continue to process the response. That can cause problems.

To reproduce this problem, take a clean Twisted installation from trunk and start the twistd web server, serving the twisted codebase: twistd -n web --path .

Then, put this in a file:

import socket
import time
data = (
    b'GET / HTTP/1.1\r\n'
    b'Host: localhost\r\n'
    b'Headername \r\n'

s = socket.create_connection(('localhost', 8080))
time.sleep(0.3)  # Let the socket layer do its thing.
print s.recv(65535)

As you can see, the last header in the block contains no colon, leading the block to be incorrectly formatted. The expected result of receiving this is that the terminal prints HTTP/1.1 400 Bad Request and nothing else. Instead, the terminal prints HTTP/1.1 400 Bad Request, a blank line, and also a 200 OK response to the request:

HTTP/1.1 400 Bad Request

HTTP/1.1 200 OK
Content-Length: 1418
Accept-Ranges: bytes
Server: TwistedWeb/16.1.1
Last-Modified: Fri, 18 Mar 2016 10:11:34 GMT
Date: Wed, 04 May 2016 10:38:40 GMT
Content-Type: text/x-python

#!/usr/bin/env python

# Copyright (c) Twisted Matrix Laboratories.
# See LICENSE for details.

Setuptools installer for Twisted.

import os
import sys
import setuptools

# Tell Twisted not to enforce zope.interface requirement on import, since
# we're going to have to import twisted.python.dist and can rely on
# setuptools to install dependencies.

def main(args):
    Invoke twisted.python.dist with the appropriate metadata about the
    Twisted package.
    # On Python 3, use until Python 3 port is done:
    if sys.version_info[0] > 2:
        import setup3

    if os.path.exists('twisted'):
        sys.path.insert(0, '.')

    requirements = ["zope.interface >= 3.6.0"]

    from twisted.python.dist import (
        STATIC_PACKAGE_METADATA, getExtensions, getScripts,
        setup, _EXTRAS_REQUIRE)

    setup_args = STATIC_PACKAGE_METADATA.copy()



if __name__ == "__main__":
    except KeyboardInterrupt:

The twistd logs also contain a 200 response to that request.

The expected behaviour can be seen by adding a new, good header underneath the bad one. That causes twisted to *only* return the 400, and to otherwise not dispatch the request.

#8304 fixed twisted.enterprise.adbapi has a lot of simple twistedchecker errors hawkowl hawkowl

A whole bunch of these are easily solved, like the newlines and the docstrings lacking links.

#8300 fixed Pass down write callable in t.w.template mithrandi mithrandi

Currently the inner flattening loop in t.w.template yields a lot of tiny strings, which has a lot of overhead. However, the outer flattening loop just passes these strings to a write callable, so we can optimize this by passing write down into the inner flattener and calling it directly. A similar optimization in Nevow yielded a significant performance improvement on PyPy (and a modest one even on CPython).

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. Filters are separated by ampersands (&). Each filter 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 omitted 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, TicketQuery

Last modified 7 months ago Last modified on 09/24/2015 10:22:29 PM