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:	9	[[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:	351	[[TicketQuery(status=closed,resolution=invalid,count)]]
Number of worksforme tickets:	47	[[TicketQuery(status=closed,resolution=worksforme,count)]]
Number of duplicate tickets:	136	[[TicketQuery(status=closed,resolution=duplicate,count)]]
Number of wontfix tickets:	231	[[TicketQuery(status=closed,resolution=wontfix,count)]]
Number of fixed tickets:	4235	[[TicketQuery(status=closed,resolution=fixed,count)]]
Number of untriaged tickets (milestone unset):	0	[[TicketQuery(status!=closed,milestone=,count)]]
Total number of tickets:	5023	[[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:	21	[[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:	#5707, #5710, #5709	[[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 highos@… bugzilla@… Summary Testing bugzilla

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:

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

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

Ticket	Resolution	Summary	Owner	Reporter
#5704	fixed	libcap-2.76	lfs-book	Bruce Dubbs
#5703	fixed	perl-5.40.2	lfs-book	Douglas R. Reno
#5702	fixed	grep-3.12	lfs-book	Bruce Dubbs

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

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

Ticket	Resolution	Summary	Owner	Reporter
#5704	fixed	libcap-2.76	lfs-book	Bruce Dubbs
Description	New minor version. See ​https://wiki.linuxfromscratch.org/blfs/ticket/21438 for changes.
#5703	fixed	perl-5.40.2	lfs-book	Douglas R. Reno
Description	New point version This is a security release for a vulnerability that allows for a heap buffer overflow. ======================================================================== CVE-2024-56406 CPAN Security Group ======================================================================== CVE ID: CVE-2024-56406 Distribution: perl Versions: from 5.40.0 until 5.40.2 from 5.38.0 until 5.38.4 from 5.36.0 through 5.36.3 from 5.34.0 through 5.34.3 MetaCPAN: https://metacpan.org/dist/perl VCS Repo: https://github.com/Perl/perl5/ Perl 5.34, 5.36, 5.38 and 5.40 are vulnerable to a heap buffer overflow when transliterating non-ASCII bytes Description ----------- A heap buffer overflow vulnerability was discovered in Perl. When there are non-ASCII bytes in the left-hand-side of the `tr` operator, `S_do_trans_invmap` can overflow the destination pointer `d`. $ perl -e '$_ = "\x{FF}" x 1000000; tr/\xFF/\x{100}/;' Segmentation fault (core dumped) It is believed that this vulnerability can enable Denial of Service and possibly Code Execution attacks on platforms that lack sufficient defenses. Problem types ------------- CWE-122 Heap-based Buffer Overflow CWE-787 Out-of-bounds Write Mitigations ----------- Users should update perl to 5.40.2 or 5.38.4, or apply the upstream patch provided in the References section. References ---------- https://github.com/Perl/perl5/commit/87f42aa0e0096e9a346c9672aa3a0bd3bef8c1dd.patch https://metacpan.org/release/SHAY/perl-5.38.4/changes https://metacpan.org/release/SHAY/perl-5.40.2/changes Credits ------- Nathan Mills, finder -- Stig Palmquist Systems that are impacted will have a segmentation fault when running the following command: perl -e '$_ = "\x{FF}" x 1000000; tr/\xFF/\x{100}/;' On an LFS 12.3 system, that returns: renodr [ /sources ]$ perl -e '$_ = "\x{FF}" x 1000000; tr/\xFF/\x{100}/;' Segmentation fault (core dumped)
#5702	fixed	grep-3.12	lfs-book	Bruce Dubbs
Description	New minor version. NEWS Noteworthy changes in release 3.12 (2025-04-10) [stable] Bug fixes Searching a directory with at least 100,000 entries no longer fails with "Operation not supported" and exit status 2. Now, this prints 1 and no diagnostic, as expected: $ mkdir t && cd t && seq 100000|xargs touch && grep -r x .; echo $? 1 [bug introduced in grep 3.11] -mN where 1 < N no longer mistakenly lseeks to end of input merely because standard output is /dev/null. Changes in behavior The --unix-byte-offsets (-u) option is gone. In grep-3.7 (2021-08-14) it became a warning-only no-op. Before then, it was a Windows-only no-op. On Windows platforms and on AIX in 32-bit mode, grep in some cases now supports Unicode characters outside the Basic Multilingual Plane.

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

---

See also: TracQuery, TracTickets, TracReports