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:

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

Ticket Resolution Summary Owner Reporter
#14013 fixed Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT) for SLED host from 4.3.20 onward (SLES11 packages broken) -- msdits9

Reported by msdits9, 40 hours ago.


We have Virtualbox installed on a number of Dell workstations and PCs, all running 64-bit SuSE Linux Enterprise Desktop. On upgrading from 4.3.18 to 4.3.20, our guest OSs (some Windows, some various flavours of linux, a mix of 32- and 64-bit) failed to boot on a number of older systems; attempting to start a guest OS leads to an immediate guest crash with a GM 1155 (VINF_EM_TRIPLE_FAULT) in the logs. This also occurs if you create a brand new guest; you can't even start installing an OS. All guests (bar the uninstalled ones, obviously) have Guest Additions installed.

The problem has continued with the upgrades to 4.3.22, 4.3.24 and 4.3.26. Back-revving to 4.3.18 allows us to boot and run our guests again.

Host Hardware tested which exhibits problem: Dell Precision T7400 - Dual Intel Xeon X5472; 12GB 800MHz DDR2; nVidia Quadro FX 570 Dell Precision T3500 - Single Intel Xeon W3530; 24GB 1333MHz DDR3; nVidia Quadro FX 580 Dell Optiplex 740 - AMD 64 X2 5000; 4GB 800MHz DDR2; nVidia GeForce 6150 LE Dell Optiplex 745 - Core 2 Duo E6600; 2GB 667MHz DDR2; Radeon X1300

Host Hardware tested which does not exhibit problem: Dell Precision T7910 - Single Xeon E5-2609; 32GB 2133MHz DDR4; nVidia Quadro K620

Attached VBox.log files for a range of guests, log name is <name of guest>_<architecture>_<version of VBox 4.3>_VBox.log

The 'newGuest' log files are the brand new guests (ie OS uninstalled)

#14011 invalid error creating Windows Server 2012 R2 in Virtual Box 4.3.26 3/16/15 release. -- FinnChick

Reported by FinnChick, 2 days ago.


I get the following error in the log file when trying to start Virtual Box and Windows Server 2012 R2. I have made sure that the appropropriate settings are enabled and disabled I in the net bios settings also. VINF_EM_TRIPLE_FAULT YOUR PC NEEDS TO RESTART. PLEASE HOLD DOWN THE POWER BUTTON . ERROR CODE: 0x000000C4

PARAMETERS: 0x0000000000000091 0x000000000000000F 0xFFFFF8019FDD9A00 0x0000000000000000

please help me.... thanks, and I have no way to attach the log file from this window.

#14008 invalid AHCI Port Reset After 1500 Hours Without Any Warnings -- tjiptomangun

Reported by tjiptomangun, 3 days ago.


Dear VirtualBox community. Our guest suddenly stop working properly after 1500 hours . First we cannot ssh into it although it is still responsive to ping request. After restart we found that guest files and /var/log/messages for the last 5 hours did not written to disk. VBox.log shows that an AHCI port reset occured 5 hours beforehand. By accident our system administrator restart the host instead of the guest, that is why there are no other information in VBox.log.1 after port reset. Unlike bug #9975 this reset did not precede by any warnings nor errors. We make a guess that this is an hard reset and from what we learn from AHCI specification, hard reset is triggered by software, which in this case is linux driver. What we don't know is why the driver reset the port. Is this because something in VD/VDI or AHCI emulation ? Please help us. Another information the host disk is configured as raid-5. Both Host and Guest are linux kernel 3.0.7

Thank you very much.

regards, tjiptomangun

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
ContactPrivacy policyTerms of Use