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:	77	[[TicketQuery(status=new&milestone=,count)]]
Number of new tickets:	88	[[TicketQuery(status=new,count)]]
Number of reopened tickets:	0	[[TicketQuery(status=reopened,count)]]
Number of assigned tickets:	8	[[TicketQuery(status=assigned,count)]]
Number of invalid tickets:	19	[[TicketQuery(status=closed,resolution=invalid,count)]]
Number of worksforme tickets:	5	[[TicketQuery(status=closed,resolution=worksforme,count)]]
Number of duplicate tickets:	11	[[TicketQuery(status=closed,resolution=duplicate,count)]]
Number of wontfix tickets:	20	[[TicketQuery(status=closed,resolution=wontfix,count)]]
Number of fixed tickets:	247	[[TicketQuery(status=closed,resolution=fixed,count)]]
Number of untriaged tickets (milestone unset):	80	[[TicketQuery(status!=closed,milestone=,count)]]
Total number of tickets:	406	[[TicketQuery(count)]]
Number of tickets reported or owned by current user:	16	[[TicketQuery(reporter=$USER,or,owner=$USER,count)]]
Number of tickets created this month:	1	[[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:	#368, #406, #360	[[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 Eric Swenson Eric Swenson Summary Add description of site_setup.sh to "How to Run Multics on DPS8M" document

Format: list

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

This is displayed as:

No results

[[TicketQuery(id=123)]]

This is displayed as:

#123

meter_signal crashes when nfaults > 1.

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

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

Ticket	Resolution	Summary	Owner	Reporter
#404	duplicate	Remove dependency on obsolete nit_data_ data segment	Eric Swenson	Eric Swenson
#402	fixed	Remove dependency on nit_data_	Eric Swenson	Eric Swenson
#401	fixed	mlsys_parse_text_ uses an old convention for handling 2-digit years	Eric Swenson	Eric Swenson

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

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

Ticket	Resolution	Summary	Owner	Reporter
#404	duplicate	Remove dependency on obsolete nit_data_ data segment	Eric Swenson	Eric Swenson
Description	The standard Mutlics mail system (>sss>bound_mail_system_) has a mechanism to check for the existence of the Inter-System Mailer (ISM), which, historically was only shipped as a separately priced product -- the TCP/IP software. The mechanism used is a linkage fault protected attempt to access nit_data_$local_host. This segment is not provided with the standard system, but only with the TCP/IP software. However, nit_data_ is now obsolete in the TCP/IP software and will not be included when the networking software is included in the next release of Multics (MR12.9). Whereas in the MIT/Honeywell TCP/IP software, there were three places where the local host name was defined (network_site_data_, network_local_data_, and nit_data_), the networking software to be included in MR12.9 will only use network_local_data_ and its subroutine interface, network_local_info_. The other two data segments were older versions and in various stages of being made obsolete. The current networking stack will no longer include network_site_data_ and nit_data_, and all references to network_local_data_ are encapsulated into the network_local_info_ subroutine. This MCR proposes to update the standard mail system to use network_local_info_$get_host_name rather than nit_data_$local_host in both the ISM-presence check, as well as the code in mlsys_nit_interface_ that attempts to determine the local system host name.
#402	fixed	Remove dependency on nit_data_	Eric Swenson	Eric Swenson
Description	The mail system has a check to determine whether the Inter-System Mailer (ISM) is installed. The ISM is part of the networking software to be installed in MR12.9. There is a linkage_error handler and a reference to nit_data_$local_host to determine whether ISM is installed. Also, the mailer determines the local host name by referencing nit_data_$local_host if the ISM is determined to be installed. nit_data_ is one of three places in the networking stacks (old and new) where the host name is defined. The other two places are network_local_data_ and network_site_data_. This resulted in three places where you had to define the local host name. In recent changes to the networking stack to be installed in MR12.9, these three locations were reduced to a single one -- network_local_data_. All references to network_site_data_ and nit_data_ have been removed. This ticket calls for removing references to nit_data_$local_host from the mail system and replacing this with linkage_error checks and calls to network_local_info_$get_local_host (which is a wrapper on top of the network_local_data_ data segment).
#401	fixed	mlsys_parse_text_ uses an old convention for handling 2-digit years	Eric Swenson	Eric Swenson
Description	mlsys_parse_text_, when parsing the email envelopes (headers), uses an old convention when encountering 2-digit years to convert to 4-digit years. It simply adds 1900 to the 2-digit year. These days, the better convention is to check for years less than 50, and for those, to add 2000, otherwise 1900.

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

---

See also: TracQuery, TracTickets, TracReports