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

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#609 fixed CC parser adds wrong address if given address is broken tboeckel Raziel
#608 fixed YAM crashes when OS detects DST change tboeckel hypex
#607 fixed Use the new title class instead of "old" register class javierdlr
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 540)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#609 fixed CC parser adds wrong address if given address is broken tboeckel Raziel


If i write (by accident, of course ;-) ) a broken address into the CC field and open that eMail after trying to send (it's not being sent, of course) in YAM's editor with "Edit", YAM or the Editor's parser is changing the broken address to soemthing else by cutting a part off and adding something on it's own, which is wrong. It's probably replacing the broken part from the 1st users eMail address or something like that.

Steps to reproduce

  1. Click on New eMail
  2. Use any eMail address in the TO field
  3. Use i.e. "A Stupid User <stupid@" as CC address (mind the missing closing >!!!)

(Also don't put the space in there, YAM's bug tracker will cut the address off, which is good :-) )

  1. Now try to send the will get caught by the throws a 501 for me, but YAM will also put the eMail into OUTGOING
  2. Mark and EDIT that eMail...the CC field is filled with "A@" for me...which is more than wrong :-)

But it shows that the parser is trying to fix the problem by taking the address from my address (i think) which happens to be

Expected results

Not really sure, maybe an error requester on sending that the format of the address is wrong or broken, just like it happens with when i miss the subject?

Actual results

Described above, plus a shortly puzzled user who asks himself wtf is wrong again with the server ;-)


No idea, never happened before though, as long as i can remember


1) It's interesting that if i write a valid address in the TO field it's still not being sent. 2) If i doubleclick the broken eMail to simply show it, the broken address is still there (so i guess it's a problem in the Editor?) 3) If i only use two words with a space, i.e. "Stupid User" the whole CC field will be erased when i open it in the Editor, three or more words and it will show up broken.

#608 fixed YAM crashes when OS detects DST change tboeckel hypex


I am using OS4.1 U6. The OS put up a message when it detected a daylight saving change. I confirmed it. Then saw YAM crashed in the background. I grabbed the reaper log.

Steps to reproduce

  1. Run YAM in background.
  2. Be in a timezone where a DST change is going to occur. :-)
  3. When OS notices DST change allow it to change clock.
  4. By now YAM should have crashed.

Expected results


Actual results

Simple crash. Recoverable.


I checked the tickets for similar cases. Found none alike. I think this may be a hidden bug I have seen before but as it only happens once a year easy to forget I had saved it. :-)

#607 fixed Use the new title class instead of "old" register class javierdlr


Can at least for AOS4 the new title class be sued insetad of "old" register class?


Files affected: TCPIPConfigPage.c, LookFeelConfigPage.c, IdentitiesConfigPage.c, FiltersConfigPage.c and WriteWindow.c (hope they are all)

Enhancement recommendation

Example for TCPIPConfigPage.c: .. #if define(amigaos4)

MUIA_ConfigPage_Contents, VGroup,

Child, TitleObject,

Child, TextObject, MUIA_Text_Contents,rtitles[0], End, Child, TextObject, MUIA_Text_Contents,rtitles[1], End,



MUIA_ConfigPage_Contents, RegisterGroup(rtitles),

MUIA_CycleChain, TRUE,

#endif ..

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 4 months ago Last modified on Jul 31, 2015, 2:17:17 PM