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:	3	[[TicketQuery(status=new&milestone=,count)]]
Number of new tickets:	3	[[TicketQuery(status=new,count)]]
Number of reopened tickets:	0	[[TicketQuery(status=reopened,count)]]
Number of assigned tickets:	1	[[TicketQuery(status=assigned,count)]]
Number of invalid tickets:	7	[[TicketQuery(status=closed,resolution=invalid,count)]]
Number of worksforme tickets:	11	[[TicketQuery(status=closed,resolution=worksforme,count)]]
Number of duplicate tickets:	1	[[TicketQuery(status=closed,resolution=duplicate,count)]]
Number of wontfix tickets:	7	[[TicketQuery(status=closed,resolution=wontfix,count)]]
Number of fixed tickets:	87	[[TicketQuery(status=closed,resolution=fixed,count)]]
Number of untriaged tickets (milestone unset):	5	[[TicketQuery(status!=closed,milestone=,count)]]
Total number of tickets:	118	[[TicketQuery(count)]]
Number of tickets reported or owned by current user:	8	[[TicketQuery(reporter=$USER,or,owner=$USER,count)]]
Number of tickets created this month:	0	[[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:	#189, #186, #185	[[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 weber weber Summary Error message "Wrong observation epoch(s)"

Format: list

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

This is displayed as:

No results

[[TicketQuery(id=123)]]

This is displayed as:

#123

BKG caster does not actively close server connections

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:

defect	84 / 87
enhancement	16 / 18
task	13 / 13

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

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

Ticket	Resolution	Summary	Owner	Reporter
#188	fixed	BNC 2.13.1 exits with option -nw	stuerze	anonym
#184	fixed	Small Typo in DecodeRTCM3MSM Method	stuerze	developer.t2r@…
#183	fixed	Additional Prometheus metrics in BKG NtripCaster	stoecker	anonymous

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

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

Ticket	Resolution	Summary	Owner	Reporter
#188	fixed	BNC 2.13.1 exits with option -nw	stuerze	anonym
Description	Version 2.13.1 (tested both Debian12 shared and compiled from source) OS: Ubuntu 24.04 BNC runs fine with GUI but trying to run it without GUI (option -nw) does not work. The program exits without any log output. The same applies to version 2.13.2 compiled from the trunk.
#184	fixed	Small Typo in DecodeRTCM3MSM Method	stuerze	developer.t2r@…
Description	Hello, I recently discovered a small issue with the DecodeRTCM3MSM method in the RTCM3Decoder class. Within this method, there is a segment of code responsible for determining the constellation type from RTCM3 messages. However, a small error/typo is causing the character 'S' to never be assigned to the "sys" variable. Problematic Code Segment (line 483 of RTCM3Decoder.cpp): else if (type >= 1101 && type <= 1007) { sys = 'S'; } The issue lies in the second part of the condition, where it checks (type <= 1007) instead of (type <= 1107), which corresponds to the SBAS MSM7 message.
#183	fixed	Additional Prometheus metrics in BKG NtripCaster	stoecker	anonymous
Description	Hi BKG team, There is a nice feature that you added in V2.0.42, that is the provision of Prometheus metrics, that we are using a lot for monitoring our BKG NtripCasters with Grafana, and we think that it would be super helpful having additional metrics to complement the current ones, in this case per mountpoint, for having a complete monitoring of the casters in real-time, like: Received bytes per mountpoint. Sent bytes per mountpoint. Number of clients per mountpoint Number of sources per mountpoint (this would be always 1 or 0 but it would help to know the current active mountpoints) Last time traffic was received per mountpoint. Last time traffic was sent per mountpoint. Received bytes per relay. Last time traffic was received per relay. Errors per relay and last time there was an error per relay? Thank you in advance! Jorge

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

---

See also: TracQuery, TracTickets, TracReports