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: | 2471 | [[TicketQuery(status=new&milestone=,count)]]
|
| Number of new tickets: | 2491 | [[TicketQuery(status=new,count)]]
|
| Number of reopened tickets: | 93 | [[TicketQuery(status=reopened,count)]]
|
| Number of assigned tickets: | 54 | [[TicketQuery(status=assigned,count)]]
|
| Number of invalid tickets: | 740 | [[TicketQuery(status=closed,resolution=invalid,count)]]
|
| Number of worksforme tickets: | 1191 | [[TicketQuery(status=closed,resolution=worksforme,count)]]
|
| Number of duplicate tickets: | 4504 | [[TicketQuery(status=closed,resolution=duplicate,count)]]
|
| Number of wontfix tickets: | 1055 | [[TicketQuery(status=closed,resolution=wontfix,count)]]
|
| Number of fixed tickets: | 11688 | [[TicketQuery(status=closed,resolution=fixed,count)]]
|
| Number of untriaged tickets (milestone unset): | 2697 | [[TicketQuery(status!=closed,milestone=,count)]]
|
| Total number of tickets: | 23447 | [[TicketQuery(count)]]
|
| Number of tickets reported or owned by current user: | 3951 | [[TicketQuery(reporter=$USER,or,owner=$USER,count)]]
|
| Number of tickets created this month: | 8 | [[TicketQuery(created=thismonth..,count)]]
|
| Number of closed Firefox tickets: | 1 | [[TicketQuery(status=closed,keywords~=firefox,count)]]
|
| Number of closed Opera tickets: | 11 | [[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: | 12 | [[TicketQuery(status=closed,keywords~=firefox|opera,count)]]
|
| Number of tickets that affect Firefox or are closed and affect Opera: | 12 | [[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: | #22930, #24392, #20302 | [[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
- Plugin actions cannot be registered and put in the toolbar
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 20715)
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 20715)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #24589 | othersoftware | Allow copying of the URL where "BROWSE action" is not supported | ||
| Description |
I use bubblewrap for isolation so I tend not to really bother with features like portals (to use flatpak terminology) INFO: Opening URL: https:// ... java.lang.UnsupportedOperationException: The BROWSE action is not supported on the current platform! Fortunately I can just pick the URL out of the terminal (since I start JOSM from the terminal) but a minor enhancement would be appreciated. |
|||
| #24579 | fixed | boundaries.osm does not contain all exclaves | ||
| Description |
Basically, I have been told the JOSM team maintains the boundaries.osm file, and I have an issue with that file. TL;DR: the boundaries.osm file does not contain all exclaves, which causes issues downstream. This may have something to do with multipolygon boundaries not being correctly extracted from OSM data. This issue was discovered downstream while reviewing the boundaries of both Hong Kong and Macao. For more background (downstream) information, (e.g. illustrative diagrams, explanations, ...), see e.g. https://github.com/westnordost/countryboundaries/issues/25 and also https://github.com/graphhopper/graphhopper/issues/3253 |
|||
| #24575 | invalid | GPX tracks imported into JOSM for Microsoft PC do not display any tags. | ||
| Description |
I record GPX tracks for mapping purposes and then use the JOSM editor to edit missing times, for example, in tunnels without GPS reception. I work with Ubuntu, macOS, and Windows 10. On my Microsoft PC, I have OpenWebStart 1.13.0 installed and JOSM version 19439 open. When I import a GPX track, whether from Insta360 or other GPX sources, and convert it to a JOSM Way, no tags are displayed. However, this works perfectly on my Ubuntu and macOS installations. |
|||
See also: TracQuery, TracTickets, TracReports
