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.

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

1 2 3
Ticket Resolution Summary Owner Reporter
#30 fixed Wiretapping draft-ietf-rtcweb-use-cases-and-requirements@… bernard_aboba@…
#25 fixed Section 5.1 Conferencing Extensions draft-ietf-rtcweb-rtp-usage@… bernard_aboba@…
#24 fixed Section 17.1 Normative reference to draft-westerlund-avtcore-transport-multiplexing draft-ietf-rtcweb-rtp-usage@… bernard_aboba@…
1 2 3

Full rows

In table format you can also have full rows by using rows=<field>:


This is displayed as:

Results (1 - 3 of 8)

1 2 3
Ticket Resolution Summary Owner Reporter
#30 fixed Wiretapping draft-ietf-rtcweb-use-cases-and-requirements@… bernard_aboba@…

In several sections of the document, the phrase "It is essential that the communication cannot be wiretapped [RFC2804]" is used. The phrase is used in Sections,,,, and, but not in (which also does not reference F20).

Given the recent revelations, and the discussion of SRTP/SDES at IETF 87, I would suggest the following:

  1. Use of more precise terminology than what is in F20. For example,

I think what we are asking for in many of the F20 scenarios is per-packet encryption and integrity protection of media, utilizing keys known only by the endpoints, as well as support for perfect forward secrecy.

  1. Inclusion of a reference to F20 in Section (Distributed

Music Band). Not sure why protection against snooping wouldn't be relevant in this use case (there are countries where musicians have been severely punished).

  1. Consideration of the requirement in gateway scenarios. For gateway scenarios such as, the e2e key management

requirement probably isn't realistic, so maybe we need to just cite F35/F36 for that case.

#25 fixed Section 5.1 Conferencing Extensions draft-ietf-rtcweb-rtp-usage@… bernard_aboba@…

These central servers can be implemented in a number of ways as discussed in Appendix A, and in the memo on RTP Topologies [I-D.westerlund-avtcore-rtp-topologies-update].

[BA] Out-of-date reference; should be to draft-ietf-avtcore-rtp-topologies-update.

o The use of video switching MCUs makes the use of RTCP for

congestion control and quality of service reports problematic(see Section 3.7 of [I-D.westerlund-avtcore-rtp-topologies-update]).

[BA] In the new document, this is now Section 3.6.2.

o RTP Transport Translators (Topo-Translator) are not of immediate

interest to WebRTC, although the main difference compared topoint to point is the possibility of seeing multiple different transport paths in any RTCP feedback.

[BA] "not of immediate interest" might be interpreted as not satisfying the requirement that "these topologies require no special RTP-layer support in the end-point if the RTP features mandated in this memo are implemented". If a browser can handle an undeclared SSRC then wouldn't an RTP translator also satisfy the requirement? For example, Section 11 states: "The API also needs to be capable of handling when new SSRCs are received but not previously signalled by signalling in some fashion."

These extensions are not necessary for interoperability; an RTP endpoint that does not implement these extensions will work correctly, but might offer poor performance.

[BA] I'd argue that not implementing the extensions will also affect aspects such as congestion control, which one might argue is necessary to "work correctly".

#24 fixed Section 17.1 Normative reference to draft-westerlund-avtcore-transport-multiplexing draft-ietf-rtcweb-rtp-usage@… bernard_aboba@…

From Section 4.4:

"One way of doing this is described in [I-D.westerlund-avtcore-transport-multiplexing]. At the time of this writing, there is no consensus to use a shim-based approach in WebRTC implementations."

[BA] Given that draft-westerlund-avtcore-transport-multiplexing doesn't have consensus, and is still an individual submission, including a normative reference to it in Section 17.1 doesn't make sense. The reference should be informative (if it is needed at all).

1 2 3

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 5 years ago Last modified on 05/11/16 15:52:10