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.

Usage

[[TicketQuery]]

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

Example	Result	Macro
Number of Triage tickets:	76	[[TicketQuery(status=new&milestone=,count)]]
Number of new tickets:	231	[[TicketQuery(status=new,count)]]
Number of reopened tickets:	10	[[TicketQuery(status=reopened,count)]]
Number of assigned tickets:	13	[[TicketQuery(status=assigned,count)]]
Number of invalid tickets:	61	[[TicketQuery(status=closed,resolution=invalid,count)]]
Number of worksforme tickets:	54	[[TicketQuery(status=closed,resolution=worksforme,count)]]
Number of duplicate tickets:	45	[[TicketQuery(status=closed,resolution=duplicate,count)]]
Number of wontfix tickets:	155	[[TicketQuery(status=closed,resolution=wontfix,count)]]
Number of fixed tickets:	1817	[[TicketQuery(status=closed,resolution=fixed,count)]]
Total number of tickets:	3169	[[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:	0	[[TicketQuery(created=thismonth..,count)]]
Last 3 modified tickets:	#3000, #3169, #3170	[[TicketQuery(max=3,order=modified,desc=1,compact)]]
Details of ticket #1:		[[TicketQuery(id=1,col=id|owner|reporter,rows=summary,table)]]
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.

Example:

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

This is displayed as:

#109

Main site: Newsbox only works for English language

#297

Create a new email list for LiveDVD discussions

#340

OSGeo4w trac instance has old logo

#361

Implement mailing list search (htdig, or likewise) on lists.osgeo.org

#501

OSGeo incubation for Orfeo Toolbox (OTB)

#547

Doxygen page not being updated by svn prior to being generated.

#805

Unable to reach upload.osgeo.org

#811

Failed to Transfer file Method Not Allowed

#813

Dutch Chapter list on Nabble

#815

Create project email list

#1002

SVN commit seems slower than normal

#1091

set up the rasdaman.osgeo.org sub domain

#1118

Broken Link: OSGeo-Live applications Presentation

#1322

FOSS sites down (2006/7/8/10/11)

#1324

openlayers.org is down

#1411

Correction to Service Provider Directory

#1496

Create Mailing list for OsGeo Nigeria

#1524

Archive of 2014 FOSS4g website

#1538

2014.foss4g.org - Error establishing a database connection

#1593

gvSIG international mailing list

#1594

gvSIG developers mailing list in Spanish

#1756

Update /osgeo_userid info about password reset

#1819

wiki configuration downlevel WRT security releases

#1839

Replace local Trac modification by proper component

#1923

Configure https etc for wordpress instance

#1924

Configure Wordpress Plugins per vendor

#1925

Configure Backup/Restore etc for Wordpress Instance

#1926

Configure LDAP and other Auth (google, github etc) for Wordpress Instance

#1927

Configure Group permissions for content management in Wordpress

#1976

problem with wiki requiring cookies even if they are already allowed

#2101

Redirect FOSS4G-Europe web page

#2139

Migrate wiki to use of OSGeo userid LDAP

#2157

Email list for OSGEO.us forming Chapter

#2194

provide blog posts on the new webside - activate the blog aggregator for the new website

#2224

provide Dropbox replacement for Board

#2335

Cannot upload artifacts via webdav

#2360

upgrade wiki to latest stuff

#2432

Create Matrix container on osgeo3

#2435

Please upgrade NextCloud

#2473

Verify email upon editing LDAP user

#2697

Dedicated lxd container for id.osgeo.org

#2745

Upgrade nextcloud from 22.2.5 to 23.0.3

#2984

Matrix to Libera Chat bridge

#2987

foss4g2019-workshops list can be closed - no more communication needed

#3083

Error 500 on gitea ssh/gpg keys

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:

[[TicketQuery(id=123)]]

This is displayed as:

#123

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, #2194, #2224, #2335, #2360, #2432, #2435, #2473, #2697, #2745, #2984, #2987, #3083

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:

45

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

[[TicketQuery(milestone=0.12.8&group=type,format=progress)]]

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

---

See also: TracQuery, TracTickets, TracReports, TracGuide