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:	464	[[TicketQuery(status=new&milestone=,count)]]
Number of new tickets:	464	[[TicketQuery(status=new,count)]]
Number of reopened tickets:	0	[[TicketQuery(status=reopened,count)]]
Number of assigned tickets:	577	[[TicketQuery(status=assigned,count)]]
Number of invalid tickets:	5316	[[TicketQuery(status=closed,resolution=invalid,count)]]
Number of worksforme tickets:	1091	[[TicketQuery(status=closed,resolution=worksforme,count)]]
Number of duplicate tickets:	4436	[[TicketQuery(status=closed,resolution=duplicate,count)]]
Number of wontfix tickets:	4265	[[TicketQuery(status=closed,resolution=wontfix,count)]]
Number of fixed tickets:	19288	[[TicketQuery(status=closed,resolution=fixed,count)]]
Number of untriaged tickets (milestone unset):	1041	[[TicketQuery(status!=closed,milestone=,count)]]
Total number of tickets:	36463	[[TicketQuery(count)]]
Number of tickets reported or owned by current user:	1488	[[TicketQuery(reporter=$USER,or,owner=$USER,count)]]
Number of tickets created this month:	8	[[TicketQuery(created=thismonth..,count)]]
Number of closed Firefox tickets:	8	[[TicketQuery(status=closed,keywords~=firefox,count)]]
Number of closed Opera tickets:	26	[[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:	34	[[TicketQuery(status=closed,keywords~=firefox|opera,count)]]
Number of tickets that affect Firefox or are closed and affect Opera:	34	[[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:	#37154, #37224, #37245	[[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 Jacob Adrian Holovaty Summary Create architecture for anonymous sessions

Format: list

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

This is displayed as:

No results

[[TicketQuery(id=123)]]

This is displayed as:

#123

Typo in the model_api/#field-types

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:

Uncategorized	2047 / 2047
Bug	10657 / 11001
New feature	3896 / 4282
Cleanup/optimization	5608 / 5918

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 in 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 35422)

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

Ticket	Resolution	Summary	Owner	Reporter
#37247	needsnewfeatureprocess	Consider grouping the constants exported by `django.db.models` under enums		Natalia Bidart
#37243	invalid	Update design philosophies documentation with an additional DRY resource	Angiep212	Angiep212
#37242	fixed	LayerMapping doesn't handle missing times, just missing date and datetime	Jacob Walls	Jacob Walls

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 35422)

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

Ticket	Resolution	Summary	Owner	Reporter
#37247	needsnewfeatureprocess	Consider grouping the constants exported by `django.db.models` under enums		Natalia Bidart
Description	The django.db.models namespace exports a set of bare uppercase constants that carry no indication of where they apply. A reader coming across SET, SET_NULL or DO_NOTHING has no way to tell from the name alone which argument accepts it, and the groups sit next to each other in a single flat namespace. The problem grows with every new group added, as seen in ​https://github.com/django/django/pull/21696, where a rename was needed to keep one group from being mistaken for another. Enums solve this directly. Membership is visible at the call site, the valid options for a given argument are discoverable from one place, and adding a new group costs nothing in namespace clarity. Django already uses this pattern in the ORM with Deferrable, WindowFrameExclusion, the Choices classes and the internal OnConflict. An enum was proposed for the fetch modes during the review linked above. The Steering Council discussed it on 2026-08-03 and agreed the change only makes sense applied across the exported constants rather than to a single group, hence this ticket. Work involved: Not every constant is a plain value. Some are callables, some are class instances, and one is a factory. Member values need a form that preserves the current behavior. Existing migration files reference the current import paths, so the module-level names have to keep resolving. enum.Enum is already registered to EnumSerializer, so newly written migrations are covered. Naming, and whether the current names become aliases or get a deprecation path. A forum thread is likely needed before a patch, since this touches long stable API.
#37243	invalid	Update design philosophies documentation with an additional DRY resource	Angiep212	Angiep212
Description	This change updates the DRY section in the design philosophies documentation to include an additional reference for the DRY principle. The aim is to provide readers with another helpful resource while keeping the documentation consistent and informative. No functional code changes are involved; this is a documentation-only update.
#37242	fixed	LayerMapping doesn't handle missing times, just missing date and datetime	Jacob Walls	Jacob Walls
Description	When parsing GDAL LayerMapping objects, Field.as_datetime() returns None for an unset field. Both OFTDate.value and OFTDateTime.value catch the resulting unpacking TypeError, but OFTTime.value does not: For example, adjust this recently merged test data edit for #36626 (this might actually be sufficient for a regression test, since this is all I wanted to do at the time of merging): tests/gis_tests/data/has_nulls/has_nulls.geojson @@ -59 +59 @@ "type": "Feature", "properties": { "uuid": "fa2ba67c-a135-4338-b924-a9622b5d869f", - "time": "00:00:00", "integer": null, "num": null }, tests/gis_tests/gdal_tests/test_ds.py @@ -110 +110 @@ None, datetime.strptime("2018-11-29T03:02:52", datetime_format), ], - "time": [time(11, 32, 14, 123000), time(0), time(3, 2, 52)], + "time": [time(11, 32, 14, 123000), None, time(3, 2, 52)], }, fids=range(3), ), File "/django/source/tests/gis_tests/gdal_tests/test_ds.py", line 199, in test03a_layers self.assertEqual(fld_value, layer.get_fields(fld_name)) File "/django/source/django/contrib/gis/gdal/layer.py", line 212, in get_fields return [feat.get(field_name) for feat in self] ^^^^^^^^^^^^^^^ File "/django/source/django/contrib/gis/gdal/feature.py", line 113, in get return self[field_name].value ^^^^^^^^^^^^^^^ File "/django/source/django/contrib/gis/gdal/field.py", line 216, in value yy, mm, dd, hh, mn, ss, tz = self.as_datetime() ^^^^^^^^^^^ TypeError: cannot unpack non-iterable NoneType object Seems like a minor oversight in 75d627888bf42f8de6064a0bd665c98c0df66c55 (#30020).

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

---

See also: TracQuery, TracTickets, TracReports