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: | 7 | [[TicketQuery(status=new&milestone=,count)]]
|
| Number of new tickets: | 58 | [[TicketQuery(status=new,count)]]
|
| Number of reopened tickets: | 0 | [[TicketQuery(status=reopened,count)]]
|
| Number of assigned tickets: | 3 | [[TicketQuery(status=assigned,count)]]
|
| Number of invalid tickets: | 28 | [[TicketQuery(status=closed,resolution=invalid,count)]]
|
| Number of worksforme tickets: | 6 | [[TicketQuery(status=closed,resolution=worksforme,count)]]
|
| Number of duplicate tickets: | 10 | [[TicketQuery(status=closed,resolution=duplicate,count)]]
|
| Number of wontfix tickets: | 40 | [[TicketQuery(status=closed,resolution=wontfix,count)]]
|
| Number of fixed tickets: | 436 | [[TicketQuery(status=closed,resolution=fixed,count)]]
|
| Number of untriaged tickets (milestone unset): | 7 | [[TicketQuery(status!=closed,milestone=,count)]]
|
| Total number of tickets: | 593 | [[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: | #1061, #1183, #833 | [[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
- PPC: Textual blur in 10.7.4 (32bit) and 10.8.4 (Multilib) (Cfg dynlinker)
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 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 532)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1187 | migratedtogithub | MPC download link is wrong | ||
| #1186 | migratedtogithub | MIPS endianness sed line is wrong | ||
| #1184 | migratedtogithub | Build for a QEMU target in each arch |
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 532)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1187 | migratedtogithub | MPC download link is wrong | ||
| Description |
As reported by Yasin Khalil via email, the download link for MPC is incorrect, it leads to a server error page. A more correct link would be to use: https://ftp.gnu.org/gnu/mpc/mpc-1.0.3.tar.gz |
|||
| #1186 | migratedtogithub | MIPS endianness sed line is wrong | ||
| Description |
As reported on the mailing list by Tobias: In Section 4.4 Build Variables (http://www.clfs.org/view/clfs-embedded/mips/cross-tools/variables.html) right after Table 4.2 in the Commands-Box where it says "Now we will set the architecture ... based on the target triplet provided above", the reader is advised to export CLFS_ARCH as "mips". Followed by a sed-expression which is obsolete, as the Endianess returned by the expression will always be "big", if the CLFS_ARCH is exported as "mips" just one line earlier - however, one might set the CLFS_ARCH to "mipsel" based on the instructional text which references the Table above. In latter case, the Endianess would indeed return "little", allthough the remainder of the Book an invalid CLFS_ARCH set to "mipsel" would fail any Compilation attempts. |
|||
| #1184 | migratedtogithub | Build for a QEMU target in each arch | ||
| Description |
We should have the default flow of the embedded book be that you're building an embedded system which can be booted in QEMU. In this way, we can give a set of commands that people can blindly follow and then boot their system using QEMU. This is advantageous as we can also enumerate what other ways things can be done for specific variants of processors/boards but at least it's easy to have someone build and run a system even if they don't have any hardware. It'll also make it easier to track down bugs as we can ask bug reporters to provide steps to reproduce using the QEMU targets. By doing this, we can provide a given kernel config and bootloader setup (if one is even needed). People who want to build and run on real hardware can then go off and figure out how their hardware works for these tasks, since embedded things are a bit less standardized compared to desktop PCs. |
|||
See also: TracQuery, TracTickets, TracReports
