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:	644	[[TicketQuery(status=new&milestone=,count)]]
Number of new tickets:	644	[[TicketQuery(status=new,count)]]
Number of reopened tickets:	0	[[TicketQuery(status=reopened,count)]]
Number of assigned tickets:	415	[[TicketQuery(status=assigned,count)]]
Number of invalid tickets:	5212	[[TicketQuery(status=closed,resolution=invalid,count)]]
Number of worksforme tickets:	1073	[[TicketQuery(status=closed,resolution=worksforme,count)]]
Number of duplicate tickets:	4343	[[TicketQuery(status=closed,resolution=duplicate,count)]]
Number of wontfix tickets:	4156	[[TicketQuery(status=closed,resolution=wontfix,count)]]
Number of fixed tickets:	18657	[[TicketQuery(status=closed,resolution=fixed,count)]]
Number of untriaged tickets (milestone unset):	1059	[[TicketQuery(status!=closed,milestone=,count)]]
Total number of tickets:	35480	[[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:	42	[[TicketQuery(created=thismonth..,count)]]
Number of closed Firefox tickets:	8	[[TicketQuery(status=closed,keywords~=firefox,count)]]
Number of closed Opera tickets:	25	[[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:	33	[[TicketQuery(status=closed,keywords~=firefox|opera,count)]]
Number of tickets that affect Firefox or are closed and affect Opera:	33	[[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:	#36138, #36250, #29446	[[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	2008 / 2008
Bug	10198 / 10562
New feature	3728 / 4120
Cleanup/optimization	5272 / 5574

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

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

Ticket	Resolution	Summary	Owner	Reporter
#36261	wontfix	`icontains` lookup doesn't work with case insensitive collations		Craig de Stigter
#36258	invalid	"error": "Model instances passed to related filters must be saved."		Nabih Elshabrawi
#36254	fixed	Documentation 'Selecting the current time zone' code error	YQ	YQ

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

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

Ticket	Resolution	Summary	Owner	Reporter
#36261	wontfix	`icontains` lookup doesn't work with case insensitive collations		Craig de Stigter
Description	As recommended by django's warning messages when upgrading to 4.x we replaced our use of the CITEXT db type with a case insensitive collation (specifically und-u-ks-level2) We have discovered that this prevents us from using search in the Django admin. The error we receive is NotSupportedError: nondeterministic collations are not supported for LIKE This makes sense since the collation cannot supprot case-sensitive comparison. However, django admin's search box is supposed to be case-insensitive. It explicitly uses icontains. It turns out that icontains is implemented using UPPER(fieldname) LIKE UPPER(pattern). Some of this logic is ​here (although I'm not sure where the second UPPER gets added) How to fix it? It seems that icontains (and iexact etc) comparisons should use ILIKE, which would work fine in this situation. I have looked through git and ticket history and can't find any discussion of why it's implemented using LIKE instead. Alternatively, using x LIKE y COLLATE "default" seems to avoid the issue in this case, although someone who knows more about collations should probably weigh in on what other side-effects that might have...
#36258	invalid	"error": "Model instances passed to related filters must be saved."		Nabih Elshabrawi
Description	When I run this command curl -X 'POST' \ '​http://127.0.0.1:8000/api/dcim/devices/' \ -H 'accept: application/json' \ -H 'Content-Type: application/json' \ -H 'X-CSRFToken: 7Jn26w1vTrl1lYFF7sZLRgh5xclFfTDQNw7lQthQnocdjyHA1RZNNM6JPn2SrRcC' \ -d '{ "id": 81665, "display": "1-B DIR NAMERA NORTH 380KV, SHQ-2 380KV,AL LAITH 380KV", "name": "1-B DIR NAMERA NORTH 380KV, SHQ-2 380KV,AL LAITH 380KV", "device_type": 466, "device_role": 16, "tenant": 1, "platform": null, "serial": "2102300766N0J2000267", "asset_tag": null, "site": 784, "location": null, "rack": 21576, "position": 12, "face": "front", "parent_device": null, "status": "active", "airflow": null, "primary_ip": null, "primary_ip4": null, "primary_ip6": null, "cluster": null, "virtual_chassis": null, "vc_position": null, "vc_priority": null, "comments": "", "local_context_data": null, "custom_fields": {} }' I have this error "Model instances passed to related filters must be saved."
#36254	fixed	Documentation 'Selecting the current time zone' code error	YQ	YQ
Description	ValueError at /set_timezone/ Need 2 values to unpack in for loop; got 6. Request Method: GET Request URL: ​http://127.0.0.1:8000/set_timezone/ Django Version: 5.2b1 Exception Type: ValueError Exception Value: Need 2 values to unpack in for loop; got 6. common_timezones = { "London": "Europe/London", "Paris": "Europe/Paris", "New York": "America/New_York", } ... return render(request, "template.html", {"timezones": common_timezones}) ... # template.html {% for city, tz in timezones %} # Error : Need 2 values to unpack in for loop; got 6. ... it should be {% for city, tz in timezones.items %} ​https://github.com/django/django/pull/19270

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

---

See also: TracQuery, TracTickets, TracReports