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.

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

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. This also allows displaying the link and description of a single ticket:


This is displayed as:

IZ730: File open dialog should remeber last directory

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

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#1593 fixed sge_ca should use sha256 signatures by default tourist
#1591 fixed [PATCH] 8.1.9 build failure with high parallelism afif
#1590 fixed Hangs in execd status - with FIX Dave Love <…> pete.forman@…
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 418)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#1593 fixed sge_ca should use sha256 signatures by default tourist

Current versions of openssl (e.g. the one in RHEL/CentOS 7) have deprecated older, less secure signature algorithms. This includes md5, which is used by default by sge_ca when running in CSP mode. The result of this is hard-to-diagnose failures when trying to run in CSP mode on such a distribution. Examples include sge_qmaster failing to start on CentOS 7, and a CentOS 7 submit host failing when trying to talk to a CentOS 6 queue master.

Changing the default signature algorithm to sha256 seems to entirely resolve this issue.

#1591 fixed [PATCH] 8.1.9 build failure with high parallelism afif

As reported in Debian #846770 [1], gridengine fails to build if trying with 64 threads. The problem turns out to be some undeclared prerequisites for the pdc target. The attached patch fixes it for me. The patch is against the v8.1.9 code base.

Thanks and regards Afif


-- Afif Elghraoui | عفيف الغراوي


#1590 fixed Hangs in execd status - with FIX Dave Love <…> pete.forman@…

I have installed SGE 8.1.9 from RPM on SUSE 11 SP4.

PROBLEM: Running this command hangs with no output.

sudo /sbin/service sgeexecd.p6444 status

DIAGNOSIS: The cause of this is the sgeexecd script failing to set pidfile and then calling cat which now expects STDIN and so waits indefinitely.

FIX: This is the patch that I used on the script in /etc/init.d. It is a two line change that you can apply to the appropriate source file.

--- sgeexecd.p6444.orig 2016-11-18 17:42:28.000000000 +0000 +++ sgeexecd.p6444 2016-11-22 15:16:04.000000000 +0000 @@ -448,9 +448,10 @@


if [ "$status" = true ]; then

+ pidfile=$execd_run_dir/

if [ -f $pidfile ]; then

pid=cat $pidfile

  • if $utilbin_dir/checkprog $pid $name > /dev/null; then

+ if $utilbin_dir/checkprog $pid sge_execd > /dev/null; then

echo "execd (pid $pid) is running..." exit 0


VERIFY: Applying that patch causes the status subcommand to report correctly.


Pete Forman Senior Programmer

Dolphin Geophysical Limited A member of the Shearwater GeoServices? Group

Direct Dial: +44 (0) 1892 707173 / Mobile: +44 (0) 7840 797658 / pete.forman@… Brockbourne House, 77 Mount Ephraim, Tunbridge Wells, Kent, TN4 8BS, UK

No image "untitled-part.gif" attached to Ticket #1590

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

Last modified 16 months ago Last modified on 22/11/16 11:06:43