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

1 2 3 4 5 6 7 8 9 10
Ticket Resolution Summary Owner Reporter
#44 fixed Windows: print may raise an exception under pythonw.exe flip flip
#41 fixed Upgrading database from version 1 fails flip flip
#40 fixed Vespa 0.3.2 tag in SVN incorrect flip flip
1 2 3 4 5 6 7 8 9 10

Full rows

In table format you can also have full rows by using rows=<field>:


This is displayed as:

Results (1 - 3 of 30)

1 2 3 4 5 6 7 8 9 10
Ticket Resolution Summary Owner Reporter
#44 fixed Windows: print may raise an exception under pythonw.exe flip flip

Under Windows, when an app that runs under pythonw.exe prints more than 4096 bytes to stdout/stderr, Python raises a "Bad file descriptor" error. This is working as desgined, although there's been a Python ticket open on it since 2003:

End users (non-developers) under Windows use pythonw.exe launch our apps from a Desktop icon. The advantage of pythonw.exe over regular python.exe is that it doesn't open a console window to execute the app. However, under pythonw.exe, stdout and stderr are apparently fixed-size buffers that fill up after 4096 bytes.

In practice this hasn't been a problem for us because we don't print to the console during normal operations. But I happened to add some print statements in a loop (==> lots of debug output) while hacking a version of Vespa that I installed from the standard bundle, and I ran into this error.

There's a workaround in the ticket referenced above (see msg97442) and I think it's worth applying to Vespa. I doubt we'll run into this problem again, but it's really confusing if you do. One or two print statements don't cause a problem, but adding several of them (or one in a loop) does.

In addition, we can add the verbose_oc flag to vespa.ini to print lots of optimal control info to the console. Enabling that flag and running under pythonw.exe would surely raise an error.

#41 fixed Upgrading database from version 1 fails flip flip

Database version 1 was used until Vespa 0.2.0 which was the first release of RFPulse 14 months ago. The code to upgrade the database from v1 to v2 worked for a while, but it is now broken. Specifically, when trying to start any Vespa app, the upgrade fails with this error:

sqlite3.OperationalError: table results has no column named ocn_state_id

One workaround is to delete the database (see this article on how to find the database). Vespa will happily build a new one from scratch.

The problem is in in _upgrade_1(). After adding RFPulse-specific tables, it invokes util_import.PulseProjectImporter to re-create the sample pulse projects. That worked at the time the code was written. However, since then pulse projects have become more complex. Optimal control added a bunch of tables to the pulse project part of the database. util_import.PulseProjectImporter expects those tables to be there, but they're not when the database is in the process of being upgraded from version 1 to 2. Those tables didn't appear in Vespa until database version 7 (Vespa 0.3.1). Once the upgrade process is complete, it will be at version 7 and util_import.PulseProjectImporter would work, but it won't work where it's currently being called.

I'm filing this as a minor bug since anyone who encounters this bug hasn't used Vespa for a looong time and probably is not very attached to what's in their database. As a result, the workaround of deleting the database is no big deal.

#40 fixed Vespa 0.3.2 tag in SVN incorrect flip flip

I screwed up our SVN tags during the release of 0.3.3. (That was the stealth release that we made available but didn't advertise so that we could do a limited release of the Analysis alpha.) Specifically, I released 0.3.3 but tagged it as 0.3.2.

Since the tag 0.3.2 already existed, I overwrote it or combined 0.3.2 with 0.3.3. (I'm not sure what happened since I don't know what happens when one tells SVN to tag two different revisions with the same tag, but I know the result is not what we want.)

I first created the tag 0_3_2 on 24 Jan 2012 with r3004:

And I re-created 0_3_2 on 15 Feb 2012 with r3102 that should have created 0_3_3 instead:

1 2 3 4 5 6 7 8 9 10

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 2 years ago Last modified on Sep 17, 2018, 4:54:48 PM