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:	3	[[TicketQuery(status=new&milestone=,count)]]
Number of new tickets:	3	[[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:	2	[[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:	2	[[TicketQuery(status=closed,resolution=fixed,count)]]
Number of untriaged tickets (milestone unset):	3	[[TicketQuery(status!=closed,milestone=,count)]]
Total number of tickets:	7	[[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:	#6, #7, #4	[[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 somebody hwarin Summary XT-IDE not working on Amiga Janus board (bridgeboard or sidecar)

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

1 2 →

Ticket	Resolution	Summary	Owner	Reporter
#6	invalid	Windows Helper	somebody	Stanley Lawson
#5	fixed	XTIDE cannot boot from hard disk	somebody	Diederik Huys
#3	invalid	Problem formatting in 1.2 MByte drive	somebody	Detlef

1 2 →

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

1 2 →

Ticket	Resolution	Summary	Owner	Reporter
#6	invalid	Windows Helper	somebody	Stanley Lawson
Description	(spam)
#5	fixed	XTIDE cannot boot from hard disk	somebody	Diederik Huys
Description	I have a clone 80286 computer with 5MiB of RAM and a Maxtor DiamondMax Plus 8 drive. XTIDE is configured on a network card with EPROM socket. XTIDE has been configured for 1 IDE controller, with interrupts enabled. This system was working successfully before, until the drive slowed down more and more, notably during the boot process. At a given point, the computer started to hang at the point "Loading MS-DOS..." needing a hard reset. I made the following attempts: define manufacturer recommended CHS-settings in BIOS and skip XTIDE initialisation with CTRL-key : computer boots perfectly move NIC and harddisk to another (386-class) computer: computer and XTIDE both work (in 286-computer:) boot with XTIDE from A-drive. The disk is the MS-DOS 6.22 boot disk #1. The OS starts, but the install fails with "Internal Stack Overflow". as before, but skip install by pressing <F5>. This works and I get a command prompt. But the moment I access the drive (dir, chkdsk, fdisk, ...) the computer hangs with "Internal Stack Overflow" reconfigure the NIC to have its interrupt relocated from 5 to 10 (since the stack message may be related to an interrupt conflict) : no effect. re-flashing to another EPROM : no effect get fresh copies of the MS-DOS 6.22 install disks, wipe the partition table, boot from floppy without install. The moment that FDISK tries to access the disk, the computer hangs. skip XTIDE-init, install DOS on 512MiB-partition, reboot without XTIDE and do auto-config in XTIDECFG. The moment I start autoconfig, the computer freezes (no error message). As a final resort, I will try to manually configure with interrupts disabled, but theoretically this shouldn't make any difference since both IRQ lines on that computer are free anyway. Please let me know if you need further information.
#3	invalid	Problem formatting in 1.2 MByte drive	somebody	Detlef
Description	hi: formatting 1.2 Mbyte disks shows many many bad sectors only on the NuXT. No errors occur on a Pentium II PC using the identical two drives, which work properly there on. My suspicion: Error in INT 13h not deleting the double stepping that is used for 360 KB disks. And of course HD disks were used. XUB was BIOS 0.9.8

1 2 →

---

See also: TracQuery, TracTickets, TracReports