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:	2	[[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:	0	[[TicketQuery(status=closed,resolution=fixed,count)]]
Number of untriaged tickets (milestone unset):	0	[[TicketQuery(status!=closed,milestone=,count)]]
Total number of tickets:	966	[[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:	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:	#967, #966, #965	[[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 arango Summary Perfect Restart

Format: list

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

This is displayed as:

No results

[[TicketQuery(id=123)]]

This is displayed as:

#123

Inconsistent time_ref

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

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

Ticket	Resolution	Summary	Owner	Reporter
#965	Fixed	IMPORTANT: Writing Rotated winds to History and Quicksave files		arango
#964	Done	VERY IMPORTANT: Wind Minus Current revisited during ESMF coupling		arango
#963	Done	IMPORTANT: Updated ROMS Native Ice Model and added a Test Case		arango

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

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

Ticket	Resolution	Summary	Owner	Reporter
#965	Fixed	IMPORTANT: Writing Rotated winds to History and Quicksave files		arango
Description	The rotated wind variables, eastward and northward, were defined in output History and Quicksave NetCDF files but were not written. The input wind variables are rotated and averaged at RHO points when appropriate and requested in roms.in: Hout(idUair) == T ! Uwind surface U-wind Hout(idVair) == T ! Vwind surface V-wind Hout(idUaiE) == T ! Uwind_eastward surface Eastward U-wind Hout(idVaiN) == T ! Vwind_northward surface Northward V-wind ... Qout(idUair) == T ! Uair surface U-wind Qout(idVair) == T ! Vair surface V-wind Qout(idUaiE) == T ! Uwind_eastward surface Eastward U-wind Qout(idVaiN) == T ! Vwind_northward surface Northward V-wind Many thanks, John Wilkin, for bringing this issue to my attention.
#964	Done	VERY IMPORTANT: Wind Minus Current revisited during ESMF coupling		arango
Description	The ROMS and WRF NUOPC cap modules were updated to exchange surface current (Usur, Vsur) between ocean and atmosphere couple components. We are currently using the WRF code from ​https://github.com/myroms, which we applied a couple of corrections to the code submitted to its developers and will appear in future releases. As before, there will be no need to patch WRF for each release version. Test Case The Hurricane IRENE application has a new test case in the IRENE/Coupling/data_wrf_roms_wmc subdirectory. For more details, please check the link to the roms_test repository inGitHub for detailed information and instructions: ​https://github.com/myroms/roms_test/blob/main/IRENE/Coupling/data_wrf_roms_wmc/Readme.md The ROMS and WRF grids are incongruent in this test case. Since ROMS doesn't cover all the ocean points in the WRF grid (red domain below), a DATA component is used to supply such values from the 3-hour HyCOM dataset. ROMS and DATA components export surface ocean current at the cell center (RHO-points). Then, the ocean currents from DATA and ROMS are melded smoothly using the appropriate weights. Surface Ocean U-velocity Surface Ocean V-velocity The meldes surface currents are imported by WRF into variables grid%uoce and grid%voce. We will continue exploring WRF internal parameters to study the effects of the surface currents on the winds and wind stress. As shown by Renault et al. (2016), the feedback from surface ocean currents to the atmosphere is an eddy-killing effect stabilizing the Gulf Stream separation at Cape Hatteras in WRF-ROMS fully coupled applications. The result is around 0.3 N/m2 weaker surface wind stress in the core of the Gulf Stream.
#963	Done	IMPORTANT: Updated ROMS Native Ice Model and added a Test Case		arango
Description	The ROMS Native Sea Model was updated and tested with the LAKE_ICE test case. It is an idealized application 200x100x30 at 1km resolution: The location of the output stations is denoted as S1, S2, S3, S4, S5, S6, S7, and S8 and used to store the time series of the solution at hourly intervals. The vertical grid is well resolved in the upper 20m with a bathymetry range between 20-200m. ROMS is initialized on Jan-1-2010 and runs for 800 days until Apr-13-2012. Please check the following link for more information, instructions, and solution plots: ​https://github.com/myroms/roms_test/blob/main/lake_ice/Forward/Readme.md Many thanks to Scott Durski for updating and improving the existing sea ice model, which was initially written by Paul Budgell and maintained and documented by Kate Hedstrom. Many thanks to Mike Dinniman for his help in debugging and testing this new version of the sea ice model.

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

---

See also: TracQuery, TracTickets, TracReports