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: | 12 | [[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: | 354 | [[TicketQuery(status=closed,resolution=invalid,count)]]
|
| Number of worksforme tickets: | 47 | [[TicketQuery(status=closed,resolution=worksforme,count)]]
|
| Number of duplicate tickets: | 143 | [[TicketQuery(status=closed,resolution=duplicate,count)]]
|
| Number of wontfix tickets: | 234 | [[TicketQuery(status=closed,resolution=wontfix,count)]]
|
| Number of fixed tickets: | 4442 | [[TicketQuery(status=closed,resolution=fixed,count)]]
|
| Number of untriaged tickets (milestone unset): | 0 | [[TicketQuery(status!=closed,milestone=,count)]]
|
| Total number of tickets: | 5248 | [[TicketQuery(count)]]
|
| Number of tickets reported or owned by current user: | 12 | [[TicketQuery(reporter=$USER,or,owner=$USER,count)]]
|
| Number of tickets created this month: | 8 | [[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: | #5935, #5934, #5912 | [[TicketQuery(max=3,order=modified,desc=1,compact)]]
|
Details of ticket #1: |
| |
| ||
Format: list
[[TicketQuery(version=0.6|0.7&resolution=duplicate)]]
This is displayed as:
No results
[[TicketQuery(id=123)]]
This is displayed as:
- #123
- Change patches to sed's where possible
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:
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 5235)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #5929 | fixed | sqlite-autoconf sqlite-doc and 3530100 (3.53.1) | ||
| #5927 | fixed | gcc-16.1.0 | ||
| #5926 | fixed | inetutils-2.8 |
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 5235)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #5929 | fixed | sqlite-autoconf sqlite-doc and 3530100 (3.53.1) | ||
| Description |
New point version. |
|||
| #5927 | fixed | gcc-16.1.0 | ||
| Description |
New major version |
|||
| #5926 | fixed | inetutils-2.8 | ||
| Description |
New minor version # Noteworthy changes in release 2.8 (2026-04-29) [stable] ** telnetd no longer supports the --debug (-D) option. Previously, it would open a predictable file name at /tmp/telnet.debug, following it if it were a symbolic link. The data printed to it could also be controlled by a client. These behaviors could be combined to result in a local privilege escalation. Reported by Justin Swartz in <https://lists.gnu.org/r/bug-inetutils/2026-03/msg00040.html>. Guillem Jover also mentioned that another user can create the file before telnetd does, keep the file open, and snoop on sessions which may include credentials in <https://lists.gnu.org/r/bug-inetutils/2026-03/msg00048.html>. ** telnet no longer leaks the value of unexported environment variables to servers sending the NEW-ENVIRON SEND USERVAR command. Reported by Justin Swartz in <https://www.openwall.com/lists/oss-security/2026/03/13/1>. ** telnetd no longer allows clients to write past the end of a stack allocated buffer, possibly leading to remote code execution, using an SLC suboption with many triplets using function octets greater than 18. CVE-2026-32746 Reported by Adiel Sol, Arad Inbar, Erez Cohen, Nir Somech, Ben Grinberg, Daniel Lubel at DREAM Security Research Team in <https://lists.gnu.org/r/bug-inetutils/2026-03/msg00031.html>. ** telnetd now ignores all environment options by default. Environment variables passed by the new --accept-env option can bypass this restriction. This is necessary to avoid vulnerabilities similar to CVE-2026-28372, since many different environment variables can be used to escalate privileges. ** Fix telnetd remote authentication by-pass vulnerability. CVE-2026-24061 Reported by Kyu Neushwaistein. Initial patch by Paul Eggert; further improvements and security advisory by Simon Josefsson. ** Prevent privilege escalation via telnetd abusing systemd service credentials support added to the login(1) implementation of util-linux in release 2.40. CVE-2026-28372 Reported by Ron Ben Yizhak@SafeBreach in <https://lists.gnu.org/archive/html/bug-inetutils/2026-02/msg00000.html>. ** telnet: Drop everything related to TN3270. The code did not build (several missing required header files) and even if we could fix it, we have no way to test it. It may contain security vulnerabilities. ** inetd: Adds new --foreground parameter to avoid forking. See <https://codeberg.org/inetutils/inetutils/pulls/10>, patch by Guillem Jover. ** Paths uses $(runstatedir) instead of $(localstatedir)/run for PID files etc. The intention is that this is a no-op for normal installations, and the files should end up in the same paths because the default value for $(runstatedor) is $(localstatedir)/run. ** Some compiler warnings are now enabled by default. Disable with --enable-gcc-warnings=no. Based on the Gnulib manywarnings module, see <https://www.gnu.org/software/gnulib/manual/html_node/manywarnings.html>. ** configure.ac avoid implicit declaration of tcpd.h hosts_ctl. Patch and report by Mike Gilbert <floppym@gentoo.org> in <https://lists.gnu.org/archive/html/bug-inetutils/2026-03/msg00026.html>. ** tests: Improve libls test that doesn't work reliably across file systems. See <https://codeberg.org/inetutils/inetutils/pulls/9>. Note that even though we aren't building telnetd by default, we are still affected by multiple issues here. |
|||
See also: TracQuery, TracTickets, TracReports
