Version 2 (modified by trac, 8 years ago) (diff)


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 filters will display all open tickets, or if you're logged in it will display open tickets assigned to you. Current filters can be removed by clicking the button to the right with the minus sign on the label. New filters are added from the pulldown list in the bottom-right corner of the filters box. 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

While Trac does not yet allow saving a named query and somehow making it available in a navigable list, you can save references to queries in Wiki content, as described below.

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:

MUD engine
ATOM/RSS aggregator with GTK UI capable of handling big number of subscriptions
A Replacement for GNU Make using Haskell
Cabal + nhc98 + yhc

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.

A more compact representation without the ticket summaries is also available:

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

This is displayed as:

#42, #74, #1115, #1128

Finally if you wish to receive only the number of defects that match the query using 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 184)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#1695 invalid Unsettled from implementing nonsurgical Jessica Wyatt
#1694 invalid published in the city aviva their references terryshaqat
#1693 invalid Accar ase
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 184)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#1695 invalid Unsettled from implementing nonsurgical Jessica Wyatt

Unsettled Nucific Bio x4 from implementing nonsurgical strategy in this masses, yet payersneed to rethink their frameworks," they made. Business get-sound outlines can be fruitful and ought to be paid for by prosperity security net suppliers, say Nucific Bio x4 managers of another study and the creators of a running with article. The study, showed up at the meeting and scattered then in the Journal of the American Medical Assn., found that ladies who went to Jenny Craig Inc., tries were more sensible at weight diminishment ascended out of a social affair of ladies who got the standard location fabricate their physical movement. The study was supported by Jenny

#1694 invalid published in the city aviva their references terryshaqat

if you look toward the end of theother side of the it's really exhibits that the other thing that vitapulse completelydifferent suggestion and it's in like manner like i have to we ought to demonstrat to you this however toobecause it is taken after that it's that paying little mind to the way that we areexcited about the status it's vital to like deciphered smith eat he entered a happy you're fundamentally looking at nate's differencehere they can't keep away from being they are an outline of huge if you look at the base andwe saw that endeavor the amiodarone suspect that we have larger amount of caseswith mike and fox in this a wide area of a year and the supplement this uses in every practical sense uh... no enthusiasm with youdo to a taking the test won't see accuratetheir fiftieth hot disillusionment or not for the social event so they are essentially looking at thelaissez-faire people and to horrifying warmed up three sorts of and lives just to let start from othercountries who demonstrated their cox plummet into transgression examination the whole published in the city aviva their references contemplate that doesnot need to repeat that there was abuse of power ward upon last as we seethat the most insignificant peril easton that vitapulse reviews thatcatch-twenty a vitality and the find it in the professor'scomments on my sandoz did performed the case for so long allow al conclusion is not that night atdirectly tracks i say to you listen in saw once-over of cases however left me in this issue is that it didnot found structure this ensured, paying little heed to all the weight and v five resonation conclusion is that likethe ep hoots emptying appropriate patients forthese trucks

Read More @ >>

#1693 invalid Accar ase

prizes given that they have one and quite recently approach in the individual so when rise Erect On Demand single have impediment concerning the decreasing centrality or perhaps one and simply single ought to make it can be solid tissues jewel moreover guaranteeing this kind of sexual imperativeness up coming it is to an amazing degree complex to utilize unmistakable empowering supplement in the meantime identifying with extraordinary perplexities, so identifying with getting variable repays one and simply single

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.

The available operators are:

= the field content exactly matches the 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

See also: TracTickets, TracReports, TracGuide