This page documents the 1.2 release. Documentation for other releases can be found here.

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:	22	[[TicketQuery(status=new&milestone=,count)]]
Number of new tickets:	1057	[[TicketQuery(status=new,count)]]
Number of reopened tickets:	4	[[TicketQuery(status=reopened,count)]]
Number of assigned tickets:	12	[[TicketQuery(status=assigned,count)]]
Number of invalid tickets:	1514	[[TicketQuery(status=closed,resolution=invalid,count)]]
Number of worksforme tickets:	1419	[[TicketQuery(status=closed,resolution=worksforme,count)]]
Number of duplicate tickets:	2190	[[TicketQuery(status=closed,resolution=duplicate,count)]]
Number of wontfix tickets:	994	[[TicketQuery(status=closed,resolution=wontfix,count)]]
Number of fixed tickets:	4569	[[TicketQuery(status=closed,resolution=fixed,count)]]
Number of untriaged tickets (milestone unset):	24	[[TicketQuery(status!=closed,milestone=,count)]]
Total number of tickets:	12351	[[TicketQuery(count)]]
Number of tickets reported or owned by current user:	1849	[[TicketQuery(reporter=$USER,or,owner=$USER,count)]]
Number of tickets created this month:	5	[[TicketQuery(created=thismonth..,count)]]
Number of closed Firefox tickets:	13	[[TicketQuery(status=closed,keywords~=firefox,count)]]
Number of closed Opera tickets:	12	[[TicketQuery(status=closed,keywords~=opera,count)]]
Number of closed tickets affecting Firefox and Opera:	1	[[TicketQuery(status=closed,keywords~=firefox opera,count)]]
Number of closed tickets affecting Firefox or Opera:	24	[[TicketQuery(status=closed,keywords~=firefox|opera,count)]]
Number of tickets that affect Firefox or are closed and affect Opera:	25	[[TicketQuery(status=closed,keywords~=opera,or,keywords~=firefox,count)]]
Number of closed Firefox tickets that don't affect Opera:	1	[[TicketQuery(status=closed,keywords~=firefox -opera,count)]]
Last 3 modified tickets:	#13753, #13752, #13755	[[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 anonymous Summary Add a new project summary module.

Format: list

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

This is displayed as:

#181

Wiki preview injects new lines

#204

request for colour legend (or something similar) for ticket groups in reports

#226

Ticket Dependencies

#239

Link to diff of specifik wiki change instead of the page itself

#351

All ticket modifications should be tracked in timeline

#413

Installing on Windows, drive other than C:

#450

Diffviewer should try to convert the text into utf-8.

#475

merging of similar tickets

#519

Python process sometimes hangs on Windows Server 2003

#529

IE 5-6 over HTTPS broken downloads

[[TicketQuery(id=123)]]

This is displayed as:

#123

No SQL error display

Format: compact

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

This is displayed as:

#181, #204, #226, #239, #351, #413, #450, #475, #519, #529

Format: count

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

This is displayed as:

10

Format: progress

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

This is displayed as:

defect	5 / 5
enhancement	2 / 2

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

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

Ticket	Resolution	Summary	Owner	Reporter
#13754	fixed	Blame view doesn't work when the repository name has meta characters	Jun Omae	Jun Omae
#13753	fixed	blame.js is not added when blame view with an empty file	Jun Omae	Jun Omae
#13752	fixed	Error occurs when creating a report in functional tests but the test doens't fail	Jun Omae	Jun Omae

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

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

Ticket	Resolution	Summary	Owner	Reporter
#13754	fixed	Blame view doesn't work when the repository name has meta characters	Jun Omae	Jun Omae
Description	The following error is logged after clicking revision number in rev column of blame view for the repository name has meta characters. 2024-05-26 10:57:06,360 Trac[main] WARNING: [127.0.0.1] HTTPInternalServerError: 500 Trac Error (Repository 'svn&amp;amp;repos' not found), <RequestWithSession "GET '/changeset/3/svn&amp;amp;repos?annotate=%2Fnormal.txt'">, referrer 'http://127.0.0.1:3000/tracenv/browser/svn%26amp%3Brepos/normal.txt?annotate=blame' We should use to_json()|safe in the <script> tag of templates. trac/versioncontrol/templates/browser.html @@ -63 +63 @@ }); # elif file: # if file.annotate == 'blame': - enableBlame("${href.changeset()}/", "${reponame}", "${path}"); + enableBlame(${to_json(href.changeset() + '/')|safe}, ${to_json(reponame)|safe}, ${to_json(path)|safe}); # endif $('#preview table.code').enableCollapsibleColumns( $('#preview table.code thead th.content'));
#13753	fixed	blame.js is not added when blame view with an empty file	Jun Omae	Jun Omae
Description	I noticed the following javascript error raises when blame view with an empty file. 09:44:43.906 Uncaught ReferenceError: enableBlame is not defined <anonymous> https://trac.edgewall.org/browser/trunk/tracopt/__init__.py?annotate=blame&rev=8695:99
#13752	fixed	Error occurs when creating a report in functional tests but the test doens't fail	Jun Omae	Jun Omae
Description	The following error is logged when functional tests running but the test doesn't fail. 2024-05-25 02:33:34,206 Trac[report] WARNING: Exception caught while executing Report {9}: "SELECT COUNT(*) FROM (\n\r\n SELECT DISTINCT p.value AS __color__,\r\n id AS ticket,\r\n summary, component, milestone, t.type AS type,\r\n reporter, time AS created,\r\n changetime AS modified, description AS _description,\r\n priority,\r\n round(julianday('now') -\r\n julianday(changetime, 'unixepoch')) as days,\r\n resolution,\r\n owner as __group__\r\n FROM ticket t\r\n LEFT JOIN enum p ON p.name = t.priority AND\r\n p.type = 'priority'\r\n WHERE ((julianday('now') -\r\n julianday(changetime, 'unixepoch')) < 7)\r\n AND status = 'closed'\r\n ORDER BY __group__, changetime, p.value\r\n \n) AS tab", args [] Traceback (most recent call last): File "/home/jun66j5/src/tracdev/svn/1.6-stable/trac/ticket/report.py", line 705, in execute_paginated_report cursor.execute(count_sql, args) File "/home/jun66j5/src/tracdev/svn/1.6-stable/trac/db/util.py", line 74, in execute return self.cursor.execute(sql) ^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/jun66j5/src/tracdev/svn/1.6-stable/trac/db/sqlite_backend.py", line 89, in execute result = PyFormatCursor.execute(self, *args) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/jun66j5/src/tracdev/svn/1.6-stable/trac/db/sqlite_backend.py", line 64, in execute return self._rollback_on_error(sqlite.Cursor.execute, sql, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/jun66j5/src/tracdev/svn/1.6-stable/trac/db/sqlite_backend.py", line 56, in _rollback_on_error return function(self, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ OperationalError: ambiguous column name: description FunctionalTester.create_report has the following TODOs: # TODO: verify the url is correct # TODO: verify the report number is correct # TODO: verify the report does not cause an internal error # TODO: verify the title appears on the report list It seems it's time to implement the TODOs.

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

---

See also: TracQuery, TracTickets, TracReports