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.

Filters

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.

Navigating Tickets

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 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.

Using TracLinks

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.

Example:

[[TicketQuery(version=0.6|0.7&resolution=duplicate)]]

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:

[[TicketQuery(id=123)]]

This is displayed as:

#123

Subcontainers of species can be deleted w/o warning

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:

0

Customizing the format

You can also customize the columns displayed in the format (format=) by using col≤field> - you can specify multiple fields and what order they are displayed by placing pipes (|) between the columns like below:

[[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter)]]

This is displayed as:

Results (1 - 3 of 603)

1 2 3 4 5 6 7 8 9 10 11 →

Ticket	Resolution	Summary	Owner	Reporter
#867	fixed	quitting arb via macro causes problems	westram	westram
#866	implemented	create database report	westram	westram
#863	implemented	allow to enumerate duplicated groups	westram	westram

1 2 3 4 5 6 7 8 9 10 11 →

Full rows

In format you can also have full rows by using rows≤field> like below:

[[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter,rows=description)]]

This is displayed as:

Results (1 - 3 of 603)

1 2 3 4 5 6 7 8 9 10 11 →

Ticket	Resolution	Summary	Owner	Reporter
#867	fixed	quitting arb via macro causes problems	westram	westram
Description	When playing back a macro which quits arb, problems arise. Reproduce: Playback a macro containing: BIO::remote_action($gb_main,'ARB_NT','ARB_NT/QUIT'); ARB::close($gb_main); Observations: BIO::remote_action never returns ARB::close is never reached socket used to communicate between ARB and the macro is not correctly closed, resulting in errors like Client (pid=14832) terminating after failure to contact database (Broken pipe).[waiting for DBENTRY 'tmp/remote/ARB_NT/authAck'] [found DBENTRY 'tmp/remote/ARB_NT/authAck'] afterwards the arb_launcher sometimes detects arb processes as 'still running'. These may be any of the following: the still running macro (probably not, it claimed to have terminated, see error above) arb_ntree; possible; arb_launcher reports: .../arb_launcher: line 25: 14820 Killed: 9 $CMD [arb_launcher[0]: 'arb_ntree --execute /Users/.../example.amc working-db.arb' has terminated with error 137] ??? after that the arb script fails to remove directories rmdir: /Users/jag22/.arb_prop/logs/20250725_012532.14911: Directory not empty This behavior is unwanted (but is expected to happen under these circumstances). if arb_ntree reports an error (see above), the whole script stops with message [press ENTER or wait 3 days] which is not useful when trying to run arb automated. Required fixes: change macro execution (of action ARB_NT/QUIT) such that the macro terminates before arb by [19513] avoid that arb_ntree is killed by arb_launcher unwise. required e.g. if merge-tool is running and has dead-locked for some reason. [optional] fix compressing logs and removal of directory add special mode for arb script, which avoids the requirement to press a key when arb crashes. Shall return different exitcode in that case. with [19515] by introducing an environment variable. avoid question "sure to quit?" by [19514]
#866	implemented	create database report	westram	westram
Description	Add a script that generates a report about data layout of a database. Scope of the report: Trees (name, leafs, groups) SAIs (name, group, alignments) Alignments (name, type, length, frequency) Selections (name, contents) Species (count, marked, fields) detailed information about fields: name, type, protections, frequency Emphasis should be placed on formatting the generated reports to facilitate comparison using diff viewers like meld or kompare.
#863	implemented	allow to enumerate duplicated groups	westram	westram
Description	Sometimes taxonomic groups are splitted into multiple clades, forming duplicated groupnames. #832 suggests to use numeric suffixes separated by ~ for such groups. ARB already supports generating such groupnames using 'group search' and an ACI using hitidx (see ​help). But this does only work for one set of duplicate groups. Tasks: implement a new ACI command allowing to be applied to all duplicates in one call (e.g. report the index inside each duplicates-cluster via dupidx) fix predefined properties supporting numeric suffixes (still using _ instead of ~)

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