wiki:TicketQuery

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: 404 [[TicketQuery(status=new,count)]]
Number of reopened tickets: 13 [[TicketQuery(status=reopened,count)]]
Number of assigned tickets: 28 [[TicketQuery(status=assigned,count)]]
Number of invalid tickets: 321 [[TicketQuery(status=closed,resolution=invalid,count)]]
Number of worksforme tickets: 173 [[TicketQuery(status=closed,resolution=worksforme,count)]]
Number of duplicate tickets: 122 [[TicketQuery(status=closed,resolution=duplicate,count)]]
Number of wontfix tickets: 367 [[TicketQuery(status=closed,resolution=wontfix,count)]]
Number of fixed tickets: 3766 [[TicketQuery(status=closed,resolution=fixed,count)]]
Number of untriaged tickets (milestone unset): 7 [[TicketQuery(status!=closed,milestone=,count)]]
Total number of tickets: 5194 [[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: 11 [[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: #5200, #5165, #5205 [[TicketQuery(max=3,order=modified,desc=1,compact)]]

Details of ticket #1:

[[TicketQuery(id=1,col=id|owner|reporter,rows=summary,table)]]

Ticket Owner Reporter
#1 a.neum...@…
Summary Review and Inclusion of the 2008-02 AsSVG() patch

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:

0

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 4749)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#5203 fixed 2.5 CI fails with postgis_upgrade.sql:125: invalid command \d.].*', strk strk
#5202 fixed It seems I can downgrade with ANY robe robe
#5199 wontfix Cannot access remote raster files when querying raster pramsey tuannguyen
1 2 3 4 5 6 7 8 9 10 11

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 4749)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#5203 fixed 2.5 CI fails with postgis_upgrade.sql:125: invalid command \d.].*', strk strk
Description

See https://dronie.osgeo.org/postgis/postgis/3354/1/2

Probably since [be4c7b69d697d0819aa68b8ca3af39a95936c1eb/git] but I don't see why (in 9.6)

References #5202

#5202 fixed It seems I can downgrade with ANY robe robe
Description

I thought we had protection for this, but maybe the protection is only in the

ALTER EXTENSION .. UPDATE;

machinery.

To test, I installed postgis 3.3.0dev.

CREATE EXTENSION postgis;

Then followed by installing postgis 3.2.2.

Then run:

SELECT postgis_extensions_upgrade();

Downgraded me to 3.2.2.

You can do the same by messing with the control files

#5199 wontfix Cannot access remote raster files when querying raster pramsey tuannguyen
Description

I'm using raster2pgsql tool to ingest raster data into Postgres database. The files are stored in Google Cloud Storage with private access. To provide access, I did following things:

  • provide keys by running
export GS_SECRET_ACCESS_KEY=<secret>

export GS_ACCESS_KEY_ID=<access id>
  • Enable related extensions and configurations
CREATE EXTENSION postgis_raster;
ALTER DATABASE postgres SET postgis.enable_outdb_rasters = true;
ALTER DATABASE postgres SET postgis.gdal_enabled_drivers TO 'ENABLE_ALL';
  • Loading raster data into database
raster2pgsql -s 990000 -t 256x256 -I -R /vsigs/<bucket>/pop12.tif pop12 | psql -h localhost -U postgres
  • provide access keys to database to read from cloud rasters
alter database postgres
SET postgis.gdal_vsi_options='GS_SECRET_ACCESS_KEY=ABC GS_ACCESS_KEY_ID=ABC'

When doing query,

select
	ST_Intersection(rast,
	ST_GeomFromEWKT('SRID=990000;POLYGON((-2764474 3232111, -2764374 3232111, -2764374 3232211, -2764474 3232211, -2764474 3232111))'))
from
	pop12
limit 1;

I got following error

ERROR:  rt_band_load_offline_data: Cannot open offline raster: /vsigs/raster-bucket/pop12.tif
CONTEXT:  SQL function "st_pixelaspolygons" statement 1
SQL statement "SELECT public.ST_Buffer(public.ST_Collect(t.geom), 0)            FROM public.ST_PixelAsPolygons(rast, nband) AS t"
PL/pgSQL function _st_intersects(geometry,raster,integer) line 21 at SQL statement
PL/pgSQL function st_intersection(geometry,raster,integer) line 11 at assignment
SQL function "st_intersection" statement 1
1 2 3 4 5 6 7 8 9 10 11


See also: TracQuery, TracTickets, TracReports

Last modified 3 months ago Last modified on May 8, 2022, 3:13:00 PM
Note: See TracWiki for help on using the wiki.