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: | 13 | [[TicketQuery(status=new&milestone=,count)]]
|
| Number of new tickets: | 433 | [[TicketQuery(status=new,count)]]
|
| Number of reopened tickets: | 15 | [[TicketQuery(status=reopened,count)]]
|
| Number of assigned tickets: | 26 | [[TicketQuery(status=assigned,count)]]
|
| Number of invalid tickets: | 350 | [[TicketQuery(status=closed,resolution=invalid,count)]]
|
| Number of worksforme tickets: | 194 | [[TicketQuery(status=closed,resolution=worksforme,count)]]
|
| Number of duplicate tickets: | 144 | [[TicketQuery(status=closed,resolution=duplicate,count)]]
|
| Number of wontfix tickets: | 427 | [[TicketQuery(status=closed,resolution=wontfix,count)]]
|
| Number of fixed tickets: | 4222 | [[TicketQuery(status=closed,resolution=fixed,count)]]
|
| Number of untriaged tickets (milestone unset): | 14 | [[TicketQuery(status!=closed,milestone=,count)]]
|
| Total number of tickets: | 5811 | [[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: | 9 | [[TicketQuery(created=thismonth..,count)]]
|
| Number of closed Firefox tickets: | 0 | [[TicketQuery(status=closed,keywords~=firefox,count)]]
|
| Number of closed Opera tickets: | 3 | [[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: | 3 | [[TicketQuery(status=closed,keywords~=firefox|opera,count)]]
|
| Number of tickets that affect Firefox or are closed and affect Opera: | 3 | [[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: | #5822, #5821, #5820 | [[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
- SQLite output format support for shp2pgsql
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 5337)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #5821 | fixed | PG18 crashing on master branch (3.6) on tickets regress | ||
| #5815 | fixed | hash operator error | ||
| #5812 | fixed | ST_Within performance regression |
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 5337)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #5821 | fixed | PG18 crashing on master branch (3.6) on tickets regress | ||
| Description |
I was seeing reds on Debbie and Github, but woodie is fine. On further inspection these appear to only be in PG18. debbie https://debbie.postgis.net/job/PostGIS_Regress/32179/consoleFull 16:25:03 psql:tickets.sql:1019: NOTICE: Hole lies outside shell at or near point 25495368.044100001 6671726.9312000005 16:25:03 #3719a|f 16:25:03 #3719b|t 16:25:03 #3774|t 16:25:03 #1014a|POINT(0 0) 16:25:03 #1014a|POINT(0 0) 16:25:03 #1014b|POINT(0 1) 16:25:03 psql:tickets.sql:1047: server closed the connection unexpectedly 16:25:03 This probably means the server terminated abnormally 16:25:03 before or while processing the request. 16:25:03 psql:tickets.sql:1047: error: connection to server was lost 16:25:03 ------------------------------------------------------------ github https://github.com/postgis/postgis/actions/runs/12323216874/job/34398402435 psql:tickets.sql:1019: NOTICE: Hole lies outside shell at or near point 25495368.044100001 6671726.9312000005 #3719a|f #3719b|t #3774|t #1014a|POINT(0 0) #1014a|POINT(0 0) #1014b|POINT(0 1) psql:tickets.sql:1047: server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. psql:tickets.sql:1047: error: connection to server was lost So they are failing on same place in 1047 which has this query SELECT '#1014c', id, st_astext(g) FROM path; |
|||
| #5815 | fixed | hash operator error | ||
| Description |
On IRC velix mentioned this bug in PostGIS 3.5.0. I haven't tested prior versions but I suspect is a regression. To generate the error: WITH lines AS (SELECT ST_GeomFromText('LINESTRING(1 2, 3 4)') AS geom
UNION ALL
SELECT ST_GeomFromText('LINESTRING(6 5, 7 8)') AS geom
)
SELECT t1.geom, t2.geom
FROM lines AS t1, lines AS t2
WHERE t1.geom <> t2.geom;
Error is - I think hash operator id might change ERROR: could not find hash function for hash operator 1192459 |
|||
| #5812 | fixed | ST_Within performance regression | ||
| Description |
ST_Within is far slower than the equivalent ST_Contains, due to a mistake in the prepgeom caching handling. |
|||
See also: TracQuery, TracTickets, TracReports
