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: | 46 | [[TicketQuery(status=new&milestone=,count)]]
|
| Number of new tickets: | 46 | [[TicketQuery(status=new,count)]]
|
| Number of reopened tickets: | 2 | [[TicketQuery(status=reopened,count)]]
|
| Number of assigned tickets: | 1 | [[TicketQuery(status=assigned,count)]]
|
| Number of invalid tickets: | 59 | [[TicketQuery(status=closed,resolution=invalid,count)]]
|
| Number of worksforme tickets: | 49 | [[TicketQuery(status=closed,resolution=worksforme,count)]]
|
| Number of duplicate tickets: | 34 | [[TicketQuery(status=closed,resolution=duplicate,count)]]
|
| Number of wontfix tickets: | 61 | [[TicketQuery(status=closed,resolution=wontfix,count)]]
|
| Number of fixed tickets: | 537 | [[TicketQuery(status=closed,resolution=fixed,count)]]
|
| Number of untriaged tickets (milestone unset): | 49 | [[TicketQuery(status!=closed,milestone=,count)]]
|
| Total number of tickets: | 845 | [[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: | 3 | [[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: | #860, #859, #861 | [[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
- Add python pyexiv2 binding
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:
defect
585 / 616
enhancement
168 / 186
task
43 / 43
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 796)
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 796)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #855 | fixed | Missing c-blosc dependency for GDAL | ||
| Description |
From GDAL IRC: "I just realized that gdal embedded in qgis for windows, up to v3.9.2, doesn't include blosc compression for zarr format" GDAL could potentially be built against https://github.com/Blosc/c-blosc
|
|||
| #854 | wontfix | Loading gdal307.dll fails, some dependencies missing/renamed | ||
| Description |
I have installed the latest OSGeo4W/QGIS, in particular gdal verision 3.9.2-1. The installation also includes gdal307-runtime (3.7.3-1).
But to me it seems gdal307.dll cannot be loaded at all, because it needs
This is according to Dependency Walker and also a third party software that tries to load gdal307.dll and fails. From Process Monitor I can see the third party process finding gdal307.dll, looking for all the deps and failing on I do have older package, that I can successfully use (gdal 3.7.3, when gdal307 was *the* main runtime). My question: Is this intended? Can it be changed? Can a third party app continue using the gdal307-runtime that comes with newer main runtime? |
|||
| #852 | invalid | Vulnerable OpenSSL v3.0.14 DLLs exist in OSGEO4W install | ||
| Description |
The latest QGIS OSGeo4W_v2 installer installs 4 OpenSSL v3.0.14 DLLs, this version is vulnerable to the following CVEs (https://openssl-library.org/news/vulnerabilities-3.0/index.html):
Evidence of my findings (using the following PowerShell): $files = 'libcrypto*.dll','libssl*.dll',’*openssl.exe’ cd 'C:\Program Files\OSGeo4W_v2\' Get-ChildItem $($files) -Recurse -Force -ErrorAction SilentlyContinue | Select-Object * -ExpandProperty VersionInfo | Sort-Object ProductVersion,FileVersionRaw,Filename | Select-Object ProductVersion,FileVersionRaw,Filename,FileDescription,CompanyName,LegalCopyright | ft -auto Results: ProductVersion FileVersionRaw FileName FileDescription CompanyName LegalCopyright -------------- -------------- -------- --------------- ----------- -------------- 3.0.14 3.0.14.0 C:\Program Files\OSGeo4W_v2\apps\Python312\DLLs\libcrypto-3-x64.dll OpenSSL library The OpenSSL Project, https://www.openssl.org/ Copyright 1998-2024 The OpenSSL Authors. All rights reserved. 3.0.14 3.0.14.0 C:\Program Files\OSGeo4W_v2\apps\Python312\DLLs\libssl-3-x64.dll OpenSSL library The OpenSSL Project, https://www.openssl.org/ Copyright 1998-2024 The OpenSSL Authors. All rights reserved. 3.0.14 3.0.14.0 C:\Program Files\OSGeo4W_v2\bin\libcrypto-3-x64.dll OpenSSL library The OpenSSL Project, https://www.openssl.org/ Copyright 1998-2024 The OpenSSL Authors. All rights reserved. 3.0.14 3.0.14.0 C:\Program Files\OSGeo4W_v2\bin\libssl-3-x64.dll OpenSSL library The OpenSSL Project, https://www.openssl.org/ Copyright 1998-2024 The OpenSSL Authors. All rights reserved. OpenSSL released version 3.0.15 on Tuesday 3rd September to fix both of the above CVEs. Please can the OpenSSL DLLs included in OSGeo4W_v2 be updated, so they use the latest OpenSSL v3.0.15 version (or v3.1.7, v3.2.3 or v3.3.2)?
Thanks in advance,
|
|||
See also: TracQuery, TracTickets, TracReports
