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: | 6 | [[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: | 1 | [[TicketQuery(status=closed,resolution=invalid,count)]]
|
| Number of worksforme tickets: | 9 | [[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: | 20 | [[TicketQuery(status=closed,resolution=fixed,count)]]
|
| Number of untriaged tickets (milestone unset): | 3 | [[TicketQuery(status!=closed,milestone=,count)]]
|
| Total number of tickets: | 41 | [[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: | #40, #41, #35 | [[TicketQuery(max=3,order=modified,desc=1,compact)]]
|
Details of ticket #1: |
| |
| ||
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:
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 34)
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 34)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #41 | NoChangeNeeded | System hangs during boot with add-in PCIe SATA card | ||
| Description |
I'm out of SATA ports on my mobo (Tyan S2895 K8WE) so I bought a PCIe 4-port SATA card with a Marvell chipset. PCI shows: Bus 129 (PCI Express), Device Number 0, Device Function 0
System boots OK with no drives connected. Adding a drive causes a hang during boot. I have recorded the debug log on another machine per the troubleshooting doc. [d:\]bldlevel os2krnl Build Level Display Facility Version 6.12.675 Sep 25 2001 (C) Copyright IBM Corporation 1993-2001 Signature: @#IBM:14.106#@_SMP IBM OS/2 Kernel Vendor: IBM Revision: 14.106 File Version: 14.106 Description: _SMP IBM OS/2 Kernel [d:\]bldlevel \os2\boot\OS2AHCI.ADD Build Level Display Facility Version 6.12.675 Sep 25 2001 (C) Copyright IBM Corporation 1993-2001 Signature: @#D Azarewicz:1.32#@##1## 10 Nov 2013 07:58:57 DAZAR1 ::::::@@AHCI
Vendor: D Azarewicz Revision: 1.32 Date/Time: 10 Nov 2013 07:58:57 Build Machine: DAZAR1 File Version: 1.32 Description: AHCI Driver (c) 2013 D Azarewicz [d:\]bldlevel \os2\boot\acpi.psd Build Level Display Facility Version 6.12.675 Sep 25 2001 (C) Copyright IBM Corporation 1993-2001 Signature: @#D Azarewicz:3.22.03#@##1## 28 Nov 2013 11:00:28 DAZAR1 ::::03::@ @ACPI based PSD for eCS (c) 2013 D Azarewicz Vendor: D Azarewicz Revision: 3.22.03 Date/Time: 28 Nov 2013 11:00:28 Build Machine: DAZAR1 File Version: 3.22.3 Description: ACPI based PSD for eCS (c) 2013 D Azarewicz I have attached the log from the other machine. Is there anything else you need? Thanks! |
|||
| #37 | worksforme | System hangs after installing AHCI 1.32 and PCIe SATA card | ||
| Description |
Tyan S2895 Thunder K8WE mainboard with 4 x nVidia SATA ports working. Installed a new PCIe 4-port SATA controller for a 2 TiB Seagate drive. System hung during boot at the time it would be doing the chkdsk on the new drive. OS2AHCI.ADD added to config.sys in front of DANIS506.ADD. Long story short, I swapped the new HD to a mainboard SATA port with a Plextor DVDRW on the new controller. Still hung, this time on OS2CDROM.DMD. I remmed that out, and it booted OK. TESTLOG was run, hopefully with some good info. |
|||
| #36 | worksforme | Unable to play or burn audio tracks on SATA drive using AHCI 1.31 | ||
| Description |
No audio cd will play using any player. Neither cdrecord nor RSJ Copy Wizard is able to burn audio tracks. iso images of Video DVDs and data CDs and DVDs burn ok. Video DVDs play ok and data CDs and DVDs can be read. In all of these cases that work it takes an inordinate amount of time for the drive to become ready as reported in ticket #35. I include a startup log as well as logs of attempts to play an audio track using both CDPM and RSJ CdView and an attempt to burn an audio CD using cdrecord. |
|||
See also: TracQuery, TracTickets, TracReports
