Version 2 (modified by trac, 9 years ago) (diff)


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

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#603 Unrelated OS/4 Compatibility diver
#602 duplicate Probleme mit Treibern der ISDN-Karte Eicon DIVA 2.01 PCI Professor
#600 fixed Unepected power off during boot; incorrect power readings; unexpected undocking behavior Lewis Rosenthal
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> like below:


This is displayed as:

Results (1 - 3 of 581)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#603 Unrelated OS/4 Compatibility diver

according to the OS/4 developer the following would be enough to be compatible with it.

In file 'krnlfix.c' function void KernelFix?(void) in the very beginning there should be:

if ((ULONG)&_KernKEEVersion > 0x10000)
   Setup.SRKrnl = 1;
   KrnlVersion = 1;
#602 duplicate Probleme mit Treibern der ISDN-Karte Eicon DIVA 2.01 PCI Professor

Der Treiber o.g. Karte verweigert den Start mit folgender Fehlermeldung:

ISDN Protocol driver TE_ETSI, Build 100-9, Protocol 6.03(V1) 99-4

Copyright Eicon Technology

DIVA 2.01 PCI found

Write to DIDD registry failed!

#600 fixed Unepected power off during boot; incorrect power readings; unexpected undocking behavior Lewis Rosenthal


IBM ThinkPad T43
2.26GHz Pentium M 780 (single core)
2GB PC-4200 RAM
Intel 82801FBM ICH6-M southbridge
ATI Radeon X300


eCS 2.1 GA
14.106_SMP retail kernel


Upon installing ACPI.PSD, while the system is still booted without any PSD loaded and while still running APM.SYS (10.163), system shuts down/powers off or goes down for reboot normally. The subsequent cold or warm boot loads the ACPI PSD, and the system boots normally. Upon then shutting down/powering off or rebooting, the subsequent boot fails, either before base device drivers begin loading (the kernel build string is still visible on-screen) or immediately after ACPIDAEMON starts. The failure is an abrupt power off. Subsequent reboots result in similar failures. Rebooting with no PSD and no APM.SYS are successful; however, until APM.SYS has been added back to CONFIG.SYS and the system successfully booted, ACPI will continue to display this behavior. Once successfully booted with APM.SYS active (ny editing CONFIG.SYS), the next reboot with ACPI and ACPIDAEMON will succeed, although rebooting or shutting down from that point will result in the original (unexpected power off) behavior.


Initially, there was no ACPID.CFG on this system. Creating one based on the sample file made no difference, and neither did specifically stating PowerButton = None (the power off event can happen long before ACPID.CFG is even read - before the IFS even loads to read any files in %ETC%).

Possibly-related symptoms:

When fully booted with ACPIDAEMON running, neither the system power object nor the Beer Battery widget are able to determine battery charge or correctly determine source. In the case of the widget, battery charge is consistently reported as 101% and on AC power (even when the system is running on battery), and the power object reports "unknown" both for power source and power state.

Finally, under normal circumstances (APM.SYS, APMDAEMN.EXE, and GSVDAEMN.EXE in CONFIG.SYS), when the system is docked (ThinkPad Dock II), the dock is locked. It is not possible to undock the machine while hot (under OS/2). Pressing the dock's release button produces a dull click, but does not release the button to its "up" position to allow it to be pressed to eject the machine - until power off, when the button will immediately snap up. Under ACPI, the button operates freely; the system does not behave as though docked. This might have some bearing on the battery state being unknown, as the system should detect that it is getting power from the docking connector, and if power is coming through the docking connector, then the system should properly "lock" to the dock.

Debug logs attached.

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