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:	0	[[TicketQuery(status=new,count)]]
Number of reopened tickets:	0	[[TicketQuery(status=reopened,count)]]
Number of assigned tickets:	0	[[TicketQuery(status=assigned,count)]]
Number of invalid tickets:	0	[[TicketQuery(status=closed,resolution=invalid,count)]]
Number of worksforme tickets:	0	[[TicketQuery(status=closed,resolution=worksforme,count)]]
Number of duplicate tickets:	0	[[TicketQuery(status=closed,resolution=duplicate,count)]]
Number of wontfix tickets:	0	[[TicketQuery(status=closed,resolution=wontfix,count)]]
Number of fixed tickets:	9	[[TicketQuery(status=closed,resolution=fixed,count)]]
Number of untriaged tickets (milestone unset):	0	[[TicketQuery(status!=closed,milestone=,count)]]
Total number of tickets:	9	[[TicketQuery(count)]]
Number of tickets reported or owned by current user:	0	[[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:	#4, #9, #8	[[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 arango Summary Analysis-Forecast Observation Impacts driver

Format: list

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

This is displayed as:

No results

[[TicketQuery(id=123)]]

This is displayed as:

No results

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

1 2 3 →

Ticket	Resolution	Summary	Owner	Reporter
#9	fixed	IMPORTANT: Corrected Sequential SP4DVAR		arango
#8	fixed	VERY IMPORTANT: Updated and cleaned Saddle-Point 4D-Var		arango
#7	fixed	VERY IMPORTANT: Updated Saddle Point 4D-Var		arango

1 2 3 →

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

1 2 3 →

Ticket	Resolution	Summary	Owner	Reporter
#9	fixed	IMPORTANT: Corrected Sequential SP4DVAR		arango
Description	Corrected saddle_point.h and atimesv.F in the sequential set-up to close the TLM and ADM history NetCDF files as the disjointed (DISJOINTED) and concurrent (DISJOINTED plus CONCURRENT_KERNEL) options.
#8	fixed	VERY IMPORTANT: Updated and cleaned Saddle-Point 4D-Var		arango
Description	The SP4DVAR algorithm is now working for sequential, disjointed, and concurrent options. The algorithm was cleaned and several small bugs were corrected, which does not affect the solution. The CPP option NOINTERP was renamed to WEAK_NOINTERP, so it is more clear and easy to distinguish. Remove the tracing capability with routine tracing.F. It was not that very helpful. Many thanks to Andy Moore for all his help in developing and testing this 4D-Var algorithm.
#7	fixed	VERY IMPORTANT: Updated Saddle Point 4D-Var		arango
Description	Continue improving the saddle-point 4D-Var to solve latency issues when writing and reading NetCDF data. Introduced SKI_REORTHO to skip the re-orthonormalization of the Arnoldi vectors in gmres.F. In some applications, it does not affect convergence or results, but it accelerates the computations. It can be done because GMRES minimization is a very robust method. Added nf90_share to netcdf_create and netcdf_open to facilitate access to a NetCDF written and read by different processes. It is only avaluable for the NetCDF-3 library. A new logical argument, Lclose, is added to def_state.F to close the file after being created to alleviate access latency between split sub-groups of PETs. A call to netcdf_sync is added to the beginning state_read.F. It Synchronizes NetCDF data to disk. It allows processes open for reading data to update the number of records written by other processes. The writer flushes buffers to disk, and the reader makes sure that it is reading from disk rather than from previously cached buffers. Reworked action=3, in atimesv.F to avoid reading TLmodVal from disk. A collected MPI communication is done in saddle_point.h instead.

1 2 3 →

---

See also: TracQuery, TracTickets, TracReports