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: | 14 | [[TicketQuery(status=new&milestone=,count)]]
|
| Number of new tickets: | 436 | [[TicketQuery(status=new,count)]]
|
| Number of reopened tickets: | 13 | [[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: | 198 | [[TicketQuery(status=closed,resolution=worksforme,count)]]
|
| Number of duplicate tickets: | 145 | [[TicketQuery(status=closed,resolution=duplicate,count)]]
|
| Number of wontfix tickets: | 431 | [[TicketQuery(status=closed,resolution=wontfix,count)]]
|
| Number of fixed tickets: | 4228 | [[TicketQuery(status=closed,resolution=fixed,count)]]
|
| Number of untriaged tickets (milestone unset): | 15 | [[TicketQuery(status!=closed,milestone=,count)]]
|
| Total number of tickets: | 5827 | [[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: | 12 | [[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: | #5838, #5837, #5836 | [[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 5352)
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 5352)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #5838 | worksforme | Possible bug in ST_Intersects | ||
| Description |
Let's have 2 lines in chain (endpoint of one is startpoint of the other) and 3rd line intersecting (one of) them very close to that point. ST_Intersects behaves badly in this case: WITH data AS
(
SELECT 'a' AS id, st_geomfromtext('LINESTRING(20.3580062 48.3096067,20.3579669 48.3096863)',4326) AS geom
UNION
SELECT 'b' AS id, st_geomfromtext('LINESTRING(20.3579669 48.3096863,20.3579264 48.3097684)',4326) AS geom
UNION
SELECT 'c' AS id, st_geomfromtext('LINESTRING(20.3580084 48.3097278,20.3579583 48.3096777)',4326) AS geom
)
SELECT
st_intersects(a.geom,b.geom) AS ab_intersects, -- true
st_intersects(a.geom,c.geom) AS ac_intersects, -- false
st_intersects(b.geom,c.geom) AS bc_intersects -- false
FROM data a, data b, data c
WHERE a.id = 'a' and b.id = 'b' and c.id = 'c';
This alone is wrong (c is clearly crossing the chain of a+b). But interestingly enough, with JOIN it gives different results (c does intersects a): WITH data AS
(
SELECT 'a' AS id, st_geomfromtext('LINESTRING(20.3580062 48.3096067,20.3579669 48.3096863)',4326) AS geom
UNION
SELECT 'b' AS id, st_geomfromtext('LINESTRING(20.3579669 48.3096863,20.3579264 48.3097684)',4326) AS geom
UNION
SELECT 'c' AS id, st_geomfromtext('LINESTRING(20.3580084 48.3097278,20.3579583 48.3096777)',4326) AS geom
)
SELECT c.id, x.id -- 3 + 1
FROM data c
JOIN data x ON st_intersects(c.geom,x.geom)
WHERE c.id='c' and x.id<>'c'
|
|||
| #5837 | duplicate | st_srid of st_union(array...) is unset ("0") but should be set to "4326" | ||
| Description |
The following query select
st_srid(st_union
(
array
[
ST_GeomFromText('polygon((131 33,132 33,132 34,131 34,131 33))', 4326)
]
))
returns for PostGIS 3.4: |
|||
| #5833 | fixed | postgis_sfcgal deprecated functions preventing pg_upgrade | ||
| Description |
We are lacking a postgis_sfcgal_legacy.c function which will keep track of all the functions we are converting to CG_. This currently results in this failure during pg_upgrade pg_restore: while PROCESSING TOC:
pg_restore: from TOC entry 1098; 1255 17648 FUNCTION st_constraineddelaunaytriangles("public"."geometry") postgres
pg_restore: error: could not execute query: ERROR: could not find function "ST_ConstrainedDelaunayTriangles" in file "/usr/pgsql-17/lib/postgis_sfcgal-3.so"
Command was: CREATE FUNCTION "public"."st_constraineddelaunaytriangles"("public"."geometry") RETURNS "public"."geometry"
LANGUAGE "c" IMMUTABLE STRICT COST 100 PARALLEL SAFE
AS '$libdir/postgis_sfcgal-3', 'ST_ConstrainedDelaunayTriangles';
-- For binary upgrade, handle extension membership the hard way
ALTER EXTENSION "postgis_sfcgal" ADD FUNCTION "public"."st_constraineddelaunaytriangles"("public"."geometry");
|
|||
See also: TracQuery, TracTickets, TracReports
