TicketQuery Wiki Macro

The TicketQuery macro lets you display ticket information anywhere that accepts WikiFormatting. The query language used by the [[TicketQuery]] macro is described in the 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.

Examples

Example	Result	Macro
Number of Triage tickets:	0	[[TicketQuery(status=new&milestone=,count)]]
Number of new tickets:	0	[[TicketQuery(status=new,count)]]
Number of reopened tickets:	1	[[TicketQuery(status=reopened,count)]]
Number of assigned tickets:	0	[[TicketQuery(status=assigned,count)]]
Number of invalid tickets:	582	[[TicketQuery(status=closed,resolution=invalid,count)]]
Number of worksforme tickets:	176	[[TicketQuery(status=closed,resolution=worksforme,count)]]
Number of duplicate tickets:	254	[[TicketQuery(status=closed,resolution=duplicate,count)]]
Number of wontfix tickets:	891	[[TicketQuery(status=closed,resolution=wontfix,count)]]
Number of fixed tickets:	4674	[[TicketQuery(status=closed,resolution=fixed,count)]]
Number of untriaged tickets (milestone unset):	0	[[TicketQuery(status!=closed,milestone=,count)]]
Total number of tickets:	6586	[[TicketQuery(count)]]
Number of tickets reported or owned by current user:	0	[[TicketQuery(reporter=$USER,or,owner=$USER,count)]]
Number of tickets created this month:	0	[[TicketQuery(created=thismonth..,count)]]
Number of closed Firefox tickets:	0	[[TicketQuery(status=closed,keywords~=firefox,count)]]
Number of closed Opera tickets:	0	[[TicketQuery(status=closed,keywords~=opera,count)]]
Number of closed tickets affecting Firefox and Opera:	0	[[TicketQuery(status=closed,keywords~=firefox opera,count)]]
Number of closed tickets affecting Firefox or Opera:	0	[[TicketQuery(status=closed,keywords~=firefox|opera,count)]]
Number of tickets that affect Firefox or are closed and affect Opera:	0	[[TicketQuery(status=closed,keywords~=opera,or,keywords~=firefox,count)]]
Number of closed Firefox tickets that don't affect Opera:	0	[[TicketQuery(status=closed,keywords~=firefox -opera,count)]]
Last 3 modified tickets:	#6959, #6303, #5752	[[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 warmerda@… warmerda@… Summary 1 bit tiff files don't work.

Format: list

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

This is displayed as:

No results

[[TicketQuery(id=123)]]

This is displayed as:

No results

Format: compact

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

This is displayed as:

No results

Format: count

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

This is displayed as:

0

Format: progress

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

This is displayed as:

Format: table

You can choose the columns displayed in the table format (format=table) using col=<field>. You can specify multiple fields and the order they are displayed by placing pipes (|) between the columns:

[[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter)]]

This is displayed as:

Results (1 - 3 of 6585)

1 2 3 4 5 6 7 8 9 10 11 →

Ticket	Resolution	Summary	Owner	Reporter
#7263	wontfix	Add gdal_fpolygonize.py	warmerdam	afantini
#7262	wontfix	enhance gdaltindex for multitemporal use	warmerdam	ruhri
#7261	fixed	GDAL XYZ Driver not recognising header field names	warmerdam	aharfoot

1 2 3 4 5 6 7 8 9 10 11 →

Full rows

In table format you can specify full rows using rows=<field>:

[[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 6585)

1 2 3 4 5 6 7 8 9 10 11 →

Ticket	Resolution	Summary	Owner	Reporter
#7263	wontfix	Add gdal_fpolygonize.py	warmerdam	afantini
Description	The gdal_polygonize.py script provides a handy interface to the function GDALPolygonize. By default this truncates float data to integer. It would be nice to have a gdal_fpolygonize.py script (or a flag to gdal_polygonize.py) that does the same using the function GDALFPolygonize, which does not truncate floats. It's extremely easy to modify gdal_polygonize.py to make it output float data. It's sufficient to replace Polygonize with FPolygonize everywhere, GetRasterBand(int(src_band_n[len('mask,'):])) with GetRasterBand(src_band_n[len('mask,'):]) and ogr.OFTInteger with ogr.OFTReal.
#7262	wontfix	enhance gdaltindex for multitemporal use	warmerdam	ruhri
Description	It would be useful, if gdaltindex could automagically add a datetime field to the shapeindex, if there is the temporal information available for the raster Datasets. For example: in Geotiff Format "TIFFTAG_DATETIME" could be evaluated.
#7261	fixed	GDAL XYZ Driver not recognising header field names	warmerdam	aharfoot
Description	I'm trying to translate gridded XYZ data files into GeoTIFFs using gdal_translate. The files do not have the data in the conventional X,Y,Z order however (it's Y,X,-,-,-,-,Z), and to avoid having to reorder columns I hoped to use the header parsing functionality documented here ​http://www.gdal.org/frmt_xyz.html I have tried the data file with TAB, space and comma separators, and all three of the suggested column name variants, but the output of gdalinfo and gdal_translate suggests that GDAL is ignoring the header row and assuming a XYZ column order in each case. I am using GDAL 2.23 installed through the OSGeo4W package installer, on Win10 x64.

1 2 3 4 5 6 7 8 9 10 11 →

---

See also: TracQuery, TracTickets, TracReports