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:	18	[[TicketQuery(status=new&milestone=,count)]]
Number of new tickets:	18	[[TicketQuery(status=new,count)]]
Number of reopened tickets:	0	[[TicketQuery(status=reopened,count)]]
Number of assigned tickets:	2	[[TicketQuery(status=assigned,count)]]
Number of invalid tickets:	7	[[TicketQuery(status=closed,resolution=invalid,count)]]
Number of worksforme tickets:	7	[[TicketQuery(status=closed,resolution=worksforme,count)]]
Number of duplicate tickets:	1	[[TicketQuery(status=closed,resolution=duplicate,count)]]
Number of wontfix tickets:	5	[[TicketQuery(status=closed,resolution=wontfix,count)]]
Number of fixed tickets:	58	[[TicketQuery(status=closed,resolution=fixed,count)]]
Number of untriaged tickets (milestone unset):	21	[[TicketQuery(status!=closed,milestone=,count)]]
Total number of tickets:	99	[[TicketQuery(count)]]
Number of tickets reported or owned by current user:	5	[[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:	#166, #165, #164	[[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	59 / 75
enhancement	9 / 12
task	10 / 12

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

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

Ticket	Resolution	Summary	Owner	Reporter
#162	invalid	couldn't setup for base station	team	anonymous
#160	invalid	ntripcaster not fetching data	team	matth8534@…
#158	invalid	How to transmit data from ntripcaster to client	stoecker	matth8534@…

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

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

Ticket	Resolution	Summary	Owner	Reporter
#162	invalid	couldn't setup for base station	team	anonymous
Description	where should I create details for base station. I assume for rover we create details inside clientmounts.aut but where for base station?
#160	invalid	ntripcaster not fetching data	team	matth8534@…
Description	I bought bkg ntripcaster recently. I created i have a user and a group assigned to that user. the same user is the admin. I created mountpoint in sourcemount.aut and entred my credentials and mountpint in the base. I eneted the mountpoint name along with / in the base too.gave ip and port as 2101. But the connection failed. I created the same mountpoint in clientmounts.aut and assigned the same group which i used first and tried again in my base but still the connection refused. Why's that happening?
#158	invalid	How to transmit data from ntripcaster to client	stoecker	matth8534@…
Description	I am sorry as it will be a newbie question. I've been assigned a task to connect my ntripcaster to client. I installed bkg ntripcaster on my server and created users and group. For testing purpose I just created one user and one group and used the group for everything. This might be a general ntripcaster question. I have to create users for my client. I created a user in users.aut. What is that command included in the ntripcaster.conf? relay pull -i user:pass -m /SYDNEY 13.127.204.219:2101/SYDNEY I dont understand this even after reading the manual. Is this user and password is referring to the client user that we created? or it is for pulling the steam from somewhere else? like a base station?

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

---

See also: TracQuery, TracTickets, TracReports