| Version 2 (modified by , 2 years ago) ( diff ) |
|---|
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: | 1 | [[TicketQuery(status=new&milestone=,count)]]
|
| Number of new tickets: | 196 | [[TicketQuery(status=new,count)]]
|
| Number of reopened tickets: | 3 | [[TicketQuery(status=reopened,count)]]
|
| Number of assigned tickets: | 1 | [[TicketQuery(status=assigned,count)]]
|
| Number of invalid tickets: | 162 | [[TicketQuery(status=closed,resolution=invalid,count)]]
|
| Number of worksforme tickets: | 95 | [[TicketQuery(status=closed,resolution=worksforme,count)]]
|
| Number of duplicate tickets: | 187 | [[TicketQuery(status=closed,resolution=duplicate,count)]]
|
| Number of wontfix tickets: | 111 | [[TicketQuery(status=closed,resolution=wontfix,count)]]
|
| Number of fixed tickets: | 1005 | [[TicketQuery(status=closed,resolution=fixed,count)]]
|
| Number of untriaged tickets (milestone unset): | 1 | [[TicketQuery(status!=closed,milestone=,count)]]
|
| Total number of tickets: | 1767 | [[TicketQuery(count)]]
|
| Number of tickets reported or owned by current user: | 1 | [[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: | #1989, #1990, #1991 | [[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:
- #123
- Option DEVISCAN does not work on OpenBSD >= 4.8
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 1560)
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 1560)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1991 | fixed | Modify SSSTC/SATA ERX-GD/CD to database (SSSTC ER5-CD3T84A) | ||
| Description |
Modify SSSTC/SATA ERX-GD/CD to database add CD480G,SGD1T92,CD960GA,SSSTC GD3T84 for ER5 |
|||
| #1990 | fixed | Add to drivedb: Acer SA100 SSDs | ||
| Description |
Request to add Acer SA100 SSDs to drivedb. The drives are manufactured by BIWIN Storage Technology. ​https://www.acerstorage.com/products/sata-25-ssd/acer-ssd-sa100/ I have several 480GB SSDs, and only one of these has the SN11873 firmware. This drive seems to be a Maxio based (variant 2) kind. The patch for this drive: --- drivedb.h.20260416 2026-04-16 08:41:00.000000000 -0600
+++ drivedb.h 2026-04-22 16:54:53.879638186 -0600
@@ -645,6 +645,7 @@
"-v 245,raw16(raw16),Bit_Error_Count"
},
{ "Maxio based SSDs (variant 2)", // MAS0902, MAS1102
+ "Acer SSD SA100 (12|24|48|96)0GB|" // tested with Acer SSD SA100 480GB/SN11873
"Fanxiang S101 ((128|256|500|512)G|[124]T)B|" // Fanxiang S101, tested with Fanxiang S101 2TB/SN14130
"FORESEE ((128|256|512)G|[12]T)B SSD|" // Foresee S58A, tested with FORESEE 512GB SSD/V1.2.7
"HP SSD S600 (120|240)GB|" // tested with HP SSD S600 240GB/SN8108
All other SA100 drives have very different firmware versions, and they seem to be well suited for the following description: { "BIWIN Storage Technology SSDs",
"Acer SSD SA100 (12|24|48|96)0GB", // tested with Acer SSD SA100 240GB/W0419B0,
// Acer SSD SA100 480GB/U0302B0 and U0401A0
"[UW]0[34]..[AB]0", "",
//"-v 1,raw48,Raw_Read_Error_Rate "
//"-v 5,raw16(raw16),Reallocated_Sector_Ct "
//"-v 9,raw24(raw8),Power_On_Hours "
//"-v 12,raw48,Power_Cycle_Count "
"-v 160,raw48,Uncorrectable_Sectors "
"-v 161,raw48,Valid_Spare_Block_Cnt "
"-v 163,raw48,Initial_Bad_Block_Count "
"-v 164,raw48,Total_Erase_Count "
"-v 165,raw48,Max_Erase_Count "
"-v 166,raw48,Min_Erase_Count "
"-v 167,raw48,Average_Erase_Count "
"-v 168,raw48,Max_Erase_Count_of_Spec "
"-v 169,raw48,Remaining_Lifetime_Perc "
//"-v 175,raw48,Program_Fail_Count_Chip "
//"-v 176,raw48,Erase_Fail_Count_Chip "
//"-v 177,raw48,Wear_Leveling_Count "
"-v 178,raw48,Runtime_Invalid_Blk_Cnt "
//"-v 181,raw48,Program_Fail_Cnt_Total "
//"-v 182,raw48,Erase_Fail_Count_Total "
//"-v 192,raw48,Power-Off_Retract_Count "
"-v 194,raw48,Device_Temperature "
//"-v 195,raw48,Hardware_ECC_Recovered "
//"-v 196,raw16(raw16),Reallocated_Event_Count "
//"-v 196,raw48,Reallocated_Event_Count "
//"-v 197,raw48,Current_Pending_Sector "
//"-v 198,raw48,Offline_Uncorrectable "
//"-v 199,raw48,UDMA_CRC_Error_Count "
//"-v 232,raw48,Available_Reservd_Space "
//"-v 241,raw48,Total_LBAs_Written "
//"-v 242,raw48,Total_LBAs_Read "
"-v 245,raw48,Flash_Writes_Sectors "
},
Both drives have exactly the same part numbers on their labels: P/N: BL.9BWWA.103 Both kinds of drives are recognized by the BIWIN Intellifence application, and corresponding SMART reports can be seen in the attached PDFs. |
|||
| #1989 | worksforme | drivedb.h update (April 2026) causes smartd crash with WD20EFRX | ||
| Description |
After automatic drivedb.h update on April 12 2026, smartd crashes immediately when monitoring a WD Red Plus (WD20EFRX-68EUZN0). Error message: malloc(): unaligned tcache chunk detected Drive details:
Environment:
Steps to reproduce:
Workarounds that fix the issue:
The March 1 drivedb.h works perfectly with the same drive and same smartd binary, confirming the bug is in the April 12 drivedb.h. |
|||
See also: TracQuery, TracTickets, TracReports
