TicketQuery Wiki Macro

The TicketQuery macro lets you display information on tickets within wiki pages. The query language used by the [[TicketQuery]] macro is described in TracQuery page.



Wiki macro listing tickets that match certain criteria.

This macro accepts a comma-separated list of keyed parameters, in the form "key=value".

If the key is the name of a field, the value must use the syntax of a filter specifier as defined in TracQuery#QueryLanguage. Note that this is not the same as the simplified URL syntax used for query: links starting with a ? character. Commas (,) can be included in field values by escaping them with a backslash (\).

Groups of field constraints to be OR-ed together can be separated by a literal or argument.

In addition to filters, several other named parameters can be used to control how the results are presented. All of them are optional.

The format parameter determines how the list of tickets is presented:

  • list -- the default presentation is to list the ticket ID next to the summary, with each ticket on a separate line.
  • compact -- the tickets are presented as a comma-separated list of ticket IDs.
  • count -- only the count of matching tickets is displayed
  • rawcount -- only the count of matching tickets is displayed, not even with a link to the corresponding query (since 1.1.1)
  • table -- a view similar to the custom query view (but without the controls)
  • progress -- a view similar to the milestone progress bars

The max parameter can be used to limit the number of tickets shown (defaults to 0, i.e. no maximum).

The order parameter sets the field used for ordering tickets (defaults to id).

The desc parameter indicates whether the order of the tickets should be reversed (defaults to false).

The group parameter sets the field used for grouping tickets (defaults to not being set).

The groupdesc parameter indicates whether the natural display order of the groups should be reversed (defaults to false).

The verbose parameter can be set to a true value in order to get the description for the listed tickets. For table format only. deprecated in favor of the rows parameter

The rows parameter can be used to specify which field(s) should be viewed as a row, e.g. rows=description|summary

The col parameter can be used to specify which fields should be viewed as columns. For table format only.

For compatibility with Trac 0.10, if there's a last positional parameter given to the macro, it will be used to specify the format. Also, using "&" as a field separator still works (except for order) but is deprecated.


Example Result Macro
Number of Triage tickets: 167 [[TicketQuery(status=new&milestone=,count)]]
Number of new tickets: 197 [[TicketQuery(status=new,count)]]
Number of reopened tickets: 12 [[TicketQuery(status=reopened,count)]]
Number of assigned tickets: 8 [[TicketQuery(status=assigned,count)]]
Number of invalid tickets: 42 [[TicketQuery(status=closed,resolution=invalid,count)]]
Number of worksforme tickets: 44 [[TicketQuery(status=closed,resolution=worksforme,count)]]
Number of duplicate tickets: 35 [[TicketQuery(status=closed,resolution=duplicate,count)]]
Number of wontfix tickets: 102 [[TicketQuery(status=closed,resolution=wontfix,count)]]
Number of fixed tickets: 1146 [[TicketQuery(status=closed,resolution=fixed,count)]]
Total number of tickets: 2366 [[TicketQuery(count)]]
Number of tickets reported or owned by current user: 2 [[TicketQuery(reporter=$USER,or,owner=$USER,count)]]
Number of tickets created this month: 4 [[TicketQuery(created=thismonth..,count)]]
Last 3 modified tickets: #2268, #2001, #2363 [[TicketQuery(max=3,order=modified,desc=1,compact)]]

Details of ticket #1:


Ticket Owner Reporter
#1 hobu warmerdam@…
Summary None

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:

Main site: Newsbox only works for English language
Create a new email list for LiveDVD discussions
OSGeo4w trac instance has old logo
Implement mailing list search (htdig, or likewise) on
OSGeo incubation for Orfeo Toolbox (OTB)
Doxygen page not being updated by svn prior to being generated.
Unable to reach
Failed to Transfer file Method Not Allowed
Dutch Chapter list on Nabble
Create project email list
SVN commit seems slower than normal
set up the sub domain
Broken Link: OSGeo-Live applications Presentation
FOSS sites down (2006/7/8/10/11)
#1324 is down
Correction to Service Provider Directory
Create Mailing list for OsGeo Nigeria
Archive of 2014 FOSS4g website
#1538 - Error establishing a database connection
gvSIG international mailing list
gvSIG developers mailing list in Spanish
Update /osgeo_userid info about password reset
wiki configuration downlevel WRT security releases
Replace local Trac modification by proper component
Configure https etc for wordpress instance
Configure Wordpress Plugins per vendor
Configure Backup/Restore etc for Wordpress Instance
Configure LDAP and other Auth (google, github etc) for Wordpress Instance
Configure Group permissions for content management in Wordpress
problem with wiki requiring cookies even if they are already allowed
Redirect FOSS4G-Europe web page
Migrate wiki to use of OSGeo userid LDAP
Email list for forming Chapter
provide Dropbox replacement for Board
Cannot upload artifacts via webdav

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. This also displays the link and description of a single ticket:


This is displayed as:

Require login to enter new tickets into MapGuide Open Source trac

A more compact representation without the ticket summaries is:

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

This is displayed as:

#109, #297, #340, #361, #501, #547, #805, #811, #813, #815, #1002, #1091, #1118, #1322, #1324, #1411, #1496, #1524, #1538, #1593, #1594, #1756, #1819, #1839, #1923, #1924, #1925, #1926, #1927, #1976, #2101, #2139, #2157, #2224, #2335

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:


A graphical use of the macro is with the format=progress attribute:


For example for one of the upcoming milestones, bars are shown by ticket type:

See also: TracQuery, TracTickets, TracReports, TracGuide

Last modified 3 years ago Last modified on Feb 1, 2017 12:38:40 AM