Trac Ticket Queries

In addition to reports, Trac provides support for custom ticket queries, which can be used to display tickets that meet specified 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 in and no name/email is 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 dropdown 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 dropdown menu of options can be added multiple times to perform an Or on 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.

After you have edited your filters, click the Update button to refresh your results.

Keyboard shortcuts are available for manipulating the checkbox filters:

  • Clicking on a filter row label toggles all checkboxes.
  • Pressing the modifier key while clicking on a filter row label inverts the state of all checkboxes.
  • Pressing the modifier key while clicking on a checkbox selects the checkbox and deselects all other checkboxes in the filter.

The modifier key is platform and browser dependent. On Mac the modified key is Option/Alt or Command. On Linux the modifier key is Ctrl + Alt. Opera on Windows seems to use Ctrl + Alt, while Alt is effective for other Windows browsers.

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

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 in by placing pipes (|) between the columns:


This is displayed as:

Results (1 - 3 of 774)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#934 fixed Fix GenericRdbms unit test baseline jng jng
#933 fixed SQL Server Requires Connect to all Databases on Server danstoica gluckett
#932 fixed WFS provider: value of number attribute is changed gregboone zhanga
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>:


This is displayed as:

Results (1 - 3 of 774)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#934 fixed Fix GenericRdbms unit test baseline jng jng

There's a whole series of backlogged patches against various GenericRdbms?-based FDO providers (primarily for OSGeo.PostgreSQL and OSGeo.SQLServerSpatial) that I'd like to see applied, but before I do that, I want to make sure the GenericRdbms? test suite baseline is all tests passing.

Currently, this is not the case. With this environment:

  • SQL Server 2017 (on Linux)
  • MySQL 5.5
  • PostgreSQL 9.5/PostGIS 2.4

We have the following failures:

SQL Server:

Test Results:
Run:  274   Failures: 4   Errors: 0

1) test: SqlServerFdoApplySchemaTest.TestSchema (F) line: 1663 Common\UnitTestUtil.cpp
 "Output file SQLServerSpatial_8759_apply_schema_test6_LPhF.xml differs from expected output file SQLServerSpatial_8759_apply_schema_test6_master.txt"

2) test: SqlServerFdoApplySchemaTest.TestOverrideErrors (F) line: 1663 Common\UnitTestUtil.cpp
 "Output file SQLServerSpatial_8759_SQLServerSpatial_8759_apply_schema_overrides_err1SP.txt differs from expected output file apply_schema_overrides_err1SP_master.txt"

3) test: SqlServerFdoApplySchemaTest.TestNoMeta (F) line: 1663 Common\UnitTestUtil.cpp
 "Output file SQLServerSpatial_8759_SQLServerSpatial_8759_apply_no_meta_err2.txt differs from expected output file apply_no_meta_err2_master.txt"

4) test: SqlServerSchemaMgrTests.testConfigError (F) line: 2051 Common\SchemaMgrTests.cpp
 "pMessage && expectedMessage.ICompare(pMessage) == 0"


Test Results:
Run:  131   Failures: 4   Errors: 0

1) test: PostGisFdoSpatialContextTest.testAxes (F) line: 190 PostGis\PostGisFdoSpatialContextTest.cpp
 "wrong part of WKT removed, see log"

2) test: PostGisSchemaMgrTests.testGenDefault (F) line: 1663 Common\UnitTestUtil.cpp
 "Output file PostGIS_8391_gen_default1.xml differs from expected output file PostGIS_8391_gen_default1_PostGIS_master.txt"

3) test: PostGisFdoApplySchemaTest.TestSchema (F) line: 1663 Common\UnitTestUtil.cpp
 "Output file PostGIS_8391_apply_schema_test6_LPhF.xml differs from expected output file PostGIS_8391_apply_schema_test6_master.txt"

4) test: PostGisFdoApplySchemaTest.TestNoMeta (F) line: 1663 Common\UnitTestUtil.cpp
 "Output file PostGIS_8391_apply_no_meta_test1.xml differs from expected output file PostGIS_8391_apply_no_meta_test1_master.xml"


Test Results:
Run:  244   Failures: 2   Errors: 1

1) test: MySqlFdoApplySchemaTest.TestSchema (F) line: 1223 Common\UnitTestUtil.cpp
 "RDBMS: Duplicate entry 'aCxdATA-Acad' for key 'f_classdef_schnm_idx'

2) test: MySqlFdoApplySchemaTest.TestOverrideErrors (F) line: 1663 Common\UnitTestUtil.cpp
 "Output file MySql_10680_MySql_10680_apply_schema_overrides_err1.txt differs from expected output file apply_schema_overrides_err1_master.txt"

3) test: MySqlReaderTest.TestExceptionalCase (E) 
 "caught unknown exception"

Most of these failures can be fixed by:

  1. General: Removing whitespace around certain master text files that are not present in the generated result
  2. General: Adding source file/line number to the <error> element of to apply_schema_test6_master.txt
  3. MySqlReaderTest?.TestExceptionalCase?: Un-expected exception due to running a SQL query using a table name in incorrect case.
  4. SqlServerSchemaMgrTests?.testConfigError: Load an alternative configuration document for the test case that does not use OracleProvider? schema mappings.
#933 fixed SQL Server Requires Connect to all Databases on Server danstoica gluckett

Within the MapGuide? Environment, SQL Server provider requires the SQL Server username to be able to connect to all databases, including "master".

This is very difficult to give a user this much power when connecting to SQL Server to an Enterprise SQL Server with a lot of live applications.

#932 fixed WFS provider: value of number attribute is changed gregboone zhanga

When connecting to a WFS server who has an attribute in xsd:long format, the value which is bigger than 2147483647 (e.g. 2555555556) is shown incorrectly in Map3D (2147483647).

It is because we use wtol to convert a string a long number. The max value is 2147483647. To fix the issue, we need to add a new method ToInt64 in class FdoStringP.

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. Filters are separated by ampersands (&). Each filter 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 omitted 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, TicketQuery

Last modified 11 months ago Last modified on Feb 1, 2017 12:34:29 AM