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.

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:

No results

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:

No results

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:

Results (1 - 3 of 356)

Ticket Resolution Summary Owner Reporter
#409 fixed Importing Movie does not show up poster chooser olivercassidy@…
#408 fixed TVRage not importing olivercassidy@…
#407 fixed scraper fails with "Imported a movie with no title" phade1

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

Ticket Resolution Summary Owner Reporter
#409 fixed Importing Movie does not show up poster chooser olivercassidy@…

Reported by olivercassidy@…, 19 months ago.


•Sapphire version 1.0b8.0.7.5 •Issue is on an ATV1 •Movies are importing - but poster selection is not working / TV Shows are importing fine

•Ran a Maintenance Update to fix this issue •Sapphire up to date •Nothing in log file •After Maintenance Update - Movie imports stopped working / TV Shows also stopped importing •Reapplied [1362] Fix #406 - to fix movie imports •Reapplied [1363] Fix #408 - to fix TV imports •Back to original problem - Movies are importing - but poster selection is not working / TV Shows are importing fine •Similar to call #401 •Attached pls find current IMDB Scraper

#408 fixed TVRage not importing olivercassidy@…

Reported by olivercassidy@…, 2 years ago.


Sapphire Version 1.0b8.0.7.4 running on AppleTV 3.0.2. TVRage scrapers have stopped working.

Failed Import Details:

  • Issue is on an ATV1
  • Movies are importing fine / TV Shows have stopped importing
  • Ran a Maintenance Update and scrapers update
  • Maintenance/scrapers update ran successfully
  • Sapphire up to date
  • Nothing in log file
  • File that is failing is "Game of Thrones S01E01.avi"
  • It is part of a series and all episodes in series do not import.
  • I have tried the import over 3 days - same result.
  • Similar to call #400
#407 fixed scraper fails with "Imported a movie with no title" phade1

Reported by phade1, 2 years ago.



running MacMini? SnowLeopard? and latest Sapphire. Updated the scrapers also.

Some new files do get detected all right via IMDB, I can select the right one, but the newly imported movies will not be displayed under Movies (or Genres aso). Some movies will not even be detected.

Looks like IMDB changed their DB format again ...

console is saying:

3/11/13 9:49:10 AM Front Row[1333] Imported a movie with no title: {

Director = (


); "IMDB Rating" = "7.5"; "MPAA Rating" = GP; "Movie ID" = tt0057076; Oscars = 0; Plot = "James Bond 007 is on the search for a Russian decoding machine, known as Lektor. Bond needs to find this machine, before the evil SPECTRE organization discovers it first. Whilst being romantically linked with Russian girl, Tatiana Romanova, Bond sneaks his way around Istanbul, whilst each SPECTRE agent tries to pick him off, including the over powering Donald 'Red' Grant and ex-KGB agent Rosa Klebb who knows all the tricks in the books and even possesses an incredible poison tipped shoe!"; Title = "";


3/11/13 9:49:16 AM Front Row[1333] Failed to import movie for /Volumes/privat/phade/My Movies/Action/James?-Bond/Leben? und Sterben lassen.avi

3/11/13 9:49:19 AM Front Row[1333] Imported a movie with no title: {

Director = (


); "IMDB Rating" = "6.2"; "MPAA Rating" = "N/A"; "Movie ID" = tt0876440; Oscars = 0; Title = "";


Kind regards, Frank

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