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:	60	[[TicketQuery(status=new&milestone=,count)]]
Number of new tickets:	80	[[TicketQuery(status=new,count)]]
Number of reopened tickets:	0	[[TicketQuery(status=reopened,count)]]
Number of assigned tickets:	13	[[TicketQuery(status=assigned,count)]]
Number of invalid tickets:	22	[[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:	273	[[TicketQuery(status=closed,resolution=fixed,count)]]
Number of untriaged tickets (milestone unset):	64	[[TicketQuery(status!=closed,milestone=,count)]]
Total number of tickets:	426	[[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:	6	[[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:	#423, #426, #166	[[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 331)

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

Ticket	Resolution	Summary	Owner	Reporter
#423	fixed	>ldd>include>host_table_dcls.incl.pl1 contains incorrect entry declarations and an unused structure	Eric Swenson	Jim Lippard
#419	invalid	telnet should accept a -port control argument to override the default telnet port	Eric Swenson	Eric Swenson
#410	fixed	bugs in message_facility_	Eric Swenson	Jim Lippard <lippard-multicstrac@…>

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

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

Ticket	Resolution	Summary	Owner	Reporter
#423	fixed	>ldd>include>host_table_dcls.incl.pl1 contains incorrect entry declarations and an unused structure	Eric Swenson	Jim Lippard
Description	The include file >ldd>include>host_table_dcls.incl.pl1 declares five entries as returning a 40-character name, which should be a 64-character name as per host_table_mgr_ itself. host_table_mgr_$address char (40) var host_table_mgr_$name_given_address char (40) var host_table_mgr_$primary_name char (40) var host_table_mgr_$shortest_name char (40) var nit_$get_forwarding_host varying char (40) The include file also contains declarations of a host_list structure and related variables that are no longer used anywhere on Multics, and a declaration for host_table_mgr_$host_list, which doesn't exist. And it is missing declarations for five other host_table_mgr_ entries which do exist.
#419	invalid	telnet should accept a -port control argument to override the default telnet port	Eric Swenson	Eric Swenson
Description	It is not possible to specify a port to connect to using the telnet protocol. We should add a -port control argument.
#410	fixed	bugs in message_facility_	Eric Swenson	Jim Lippard <lippard-multicstrac@…>
Description	Bug 1a: free_msgf_mbx_ptr, line 424 The loop searching for predecessor mailbox pointers can overshoot by one and leave a freed block on the list. A mid-chain block is freed while still linked; a last-in-chain block is neither unlinked nor freed. This can cause a process hang in the message_status command. This section of code also returns error_table_$unimplemented_version when it should return error_table_$bad_subr_arg, in the case where a supplied pointer doesn’t match message_facility_’s mailbox structures (not a version mismatch). Bug 1b: get_next_msgf_mbx_ptr, line 290 message_status passes the same variable for both ptr arguments of this entry, so assigning P_next_msgf_mbx_ptr = null () destroys the input pointer before the error recovery on line 304 reads it, causing the recovery to restart at static_msgf_mbx_ptr instead of stepping past the mailbox just freed. The fix makes a copy of the input parameter as input_msgf_mbx_ptr and uses it instead. These two bugs (1a and 1b) together cause message_status -a to loop; 1a’s fix ends the loop but will still report the mailbox twice; 1b’s fix removes the duplication but by itself doesn’t terminate the loop. (To demonstrate, create and accept messages on three mailboxes, do a message_status -all, then delete the middle mailbox and do message_status -all again.) Bug 2: wakeup_processor, line 1300 The code tests whether the operation is being done on an “own” mailbox, but calls the non-own entry regardless of the test. The effect is that accept_message wakeups don’t work on a mailbox to which the user has d and o permissions but not r, when the o should govern the outcome. Bug 3: create_message_array, line 1502 Message existence bits are indexed by array positions, but these positions shift when a newly read message is inserted below existing entries. The bit array is also sized from n_messages on entry, so the shifted index can run past its end. The fix sizes it by n_elements, shifts the bits along with the entries, and widens the array deletion pass to also match. Bug 4: get_message_index, line 1454 The binary search won’t work if there are holes in the array from deleted messages; this leads to a process hang and false reports of no message. Newly allocated msg_array elements (between n_messages and n_elements) are not cleared; the fix clears them. Bug 5: print_message, line 1159 The return P_code parameter is not set when message read fails. (The pm command reports nothing when in some cases it should, when there’s a genuine error other than error_table_$no_message.) Bug 6: set_wakeup_state, line 511 The change_state variable should be initialized at the top; current code uses it before it’s initialized. Bug 7: get_msgf_mbx_ptr, line 379 A failed open leaves the new block linked, leaving a zombie entry which compounds bug 1. Bug 8: Minor issues There’s a missing return statement in an error code ^= 0 block, there are several places where substr lengths could calculate to a negative number if senders are corrupted or missing, there’s an uninitialized mbx_index variable, and an unnecessary array copy when n_messages = 0.

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

---

See also: TracQuery, TracTickets, TracReports