Trac Ticket Queries
Table of Contents
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.
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:
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:
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:
- #35
- dynamically scoped values
- #46
- Interrupts
- #56
- letrec*
- #80
- Extended symbol/identifier syntax
- #86
- What's in the hashtable module?
- #94
- Extending identifier/symbol lexical syntax
- #98
- Semantics of REPLs
- #99
- Allow top-level LET-SYNTAX
- #110
- user-defined types (procedural)
- #128
- About value returned by if, cond, case with no else clause
- #129
- About value returned by mutation procedures
- #130
- for-each return value
- #146
- Normalization should be its own module separate from the rest of Unicode
- #179
- Unicode module should be renamed
- #190
- Clarify the language defining modules
- #192
- Add third argument to NUMBER->STRING
- #201
- Editorial: Explain better how module bodies work
- #211
- Modules at the REPL
- #228
- DEFINE-LIBRARY to replace MODULE
- #236
- Need a name for R7RS-small language and report
- #247
- Editorial: fix up table of conventional names to include char, byte, etc.
- #252
- Exceptions needs an intro
- #272
- continuations outside of Scheme
- #276
- Ordering conventions for identifiers in modules
- #314
- feature review
- #371
- Fix broken definition of expt
- #386
- Merge `write-bytevector` and `write-bytevector-partial`
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:
#35, #46, #56, #80, #86, #94, #98, #99, #110, #128, #129, #130, #146, #179, #190, #192, #201, #211, #228, #236, #247, #252, #272, #276, #314, #371, #386
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:
27
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:
[[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter)]]
This is displayed as:
Results (1 - 3 of 161)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #386 | duplicate | Merge `write-bytevector` and `write-bytevector-partial` | alexshinn | cowan |
| #377 | wontfix | Editorial: Add Riastradh's better LET-VALUES definitions | alexshinn | cowan |
| #371 | duplicate | Fix broken definition of expt | alexshinn | cowan |
Full rows
In table 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 161)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #386 | duplicate | Merge `write-bytevector` and `write-bytevector-partial` | alexshinn | cowan |
| Description |
Under this proposal, the signature would be (write-bytevector bytevector start end port), with the last three arguments optional. The only disadvantage here is that you would no longer be able to specify (write-bytevector bytevector port) directly; you'd need to say (write-bytevector bytevector 0 (bytevector-length bytevector) port). |
|||
| #377 | wontfix | Editorial: Add Riastradh's better LET-VALUES definitions | alexshinn | cowan |
| Description | ||||
| #371 | duplicate | Fix broken definition of expt | alexshinn | cowan |
| Description |
R6RS says: 0.0z is 1.0 if z = 0.0, and 0.0 if (real-part z) is positive. For other cases in which the first argument is zero, either an exception is raised with condition type &implementation-restriction, or an unspecified number object is returned. R5RS specifies behavior that is simply incorrect for z with negative real part: 0z is 1 if z = 0 and 0 otherwise. I tested the usual suite on (expt 0.0 0.0) (expt 0.0 2), and (expt 0.0 -2): Conforming implementations: Racket, Gauche, Gambit, Chicken (with and without the numbers egg), Bigloo, Kawa, Chibi, Chez, SCM, Ikarus/Vicare, Ypsilon, Mosh, NexJ, STklos, KSi, RScheme, XLisp, Rep, VX, SXM, Spark, Inlab return 1.0, 0.0, and +inf.0. Guile, Larceny return 1.0, 0.0, and +nan.0. SISC, IronScheme, Elk return 1.0, 0.0, and 0.0. UMB returns 1.0, 0.0, and an exception. Non-conforming implementations: Scheme48, BDC return an exception, 0.0, and +inf.0. Scsh returns -nan.0, 0.0, and an exception. Scheme 7 returns 0.0, 0.0, and an exception. Scheme 9 returns exact 0, 0.0, and +nan.0. Elk returns exact 1, exact 0, and exact 0. MIT returns an exception, 0.0, and another exception. SigScheme, Shoe, TinyScheme, Dream, Schemik, Oaklisp, Owl Lisp don't support inexact expt. |
|||
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
