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: | 48 | [[TicketQuery(status=new&milestone=,count)]]
|
| Number of new tickets: | 48 | [[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: | 50 | [[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: | 549 | [[TicketQuery(status=closed,resolution=fixed,count)]]
|
| Number of untriaged tickets (milestone unset): | 51 | [[TicketQuery(status!=closed,milestone=,count)]]
|
| Total number of tickets: | 860 | [[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: | 5 | [[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: | #876, #872, #875 | [[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
596 / 627
enhancement
169 / 188
task
44 / 45
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 809)
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 809)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #875 | fixed | PROJ 9.6.0 & PROJ-data 1.21 | ||
| Description |
This task is to update
See announcement https://lists.osgeo.org/pipermail/proj/2025-March/011776.html |
|||
| #873 | fixed | Apache Package - newest build (2.4.62-3) but wrong content | ||
| Description |
I have a QGIS-Server install on a Windows Server which I did more than a year ago using OSgeo4W-Installer. My IT-department noticed that the Apache version is/was quite old (2.4.58) so I updated again, using OSgeo4W-Installer. The version I could download and install was 2.4.62-3. Everything went well (except all my modified configs were overwritten) and I thought we are now running the latest Apache build. Also OSGeo4W-installer shows that the latest Apache build is installed. When I look insinde Apache Monitor as well as Apache Log, i still see the old version running (2.4.58). Then I had a look at the temporary folder where OSGeo4W-installer downlaods the package. There I found a package correctly named "apache-2.4.62-3.tar.bz2" and I had a look inside: The "components", binaries and files all still look like the old version (date modified beginning of 2024). So I have the impression, that the "new" build provided by OSGeo4W Installer still serves the old content of 2.4.58. I am confused, if am the only one noticing, or if I am doing something wrong? |
|||
| #872 | fixed | GRASS processing algorithms fail to execute | ||
| Description |
On my Microsoft Windows 10 Home 1903 18362.778 system, the GRASS (either 8.4.0-5 or 8.4.1-1) processing algorithms executed in QGIS (3.40.4-1) fail due to the crash of g.proj.exe, v.in.ogr.exe and v.out.ogr.exe e.g. for g.proj.exe: Nome dell'applicazione che ha generato l'errore: g.proj.exe, versione: 8.4.0.0, timestamp: 0x67c1b293 Nome del modulo che ha generato l'errore: MSVCP140.dll, versione: 14.32.31332.0, timestamp: 0x8b64702c Codice eccezione: 0xc0000005 Offset errore 0x00000000000132f8 ID processo che ha generato l'errore: 0x1c20 Ora di avvio dell'applicazione che ha generato l'errore: 0x01db8c3ed152c06d Percorso dell'applicazione che ha generato l'errore: C:\OS5C2A~1\apps\grass\grass84\bin\g.proj.exe Percorso del modulo che ha generato l'errore: C:\WINDOWS\SYSTEM32\MSVCP140.dll ID segnalazione: a8036716-e21d-46f7-9d3e-2b79d6dea9cc Nome completo pacchetto che ha generato l'errore: ID applicazione relativo al pacchetto che ha generato l'errore: Bucket errato 1274638728505842915, tipo 4 Nome evento: APPCRASH Risposta: Non disponibile ID CAB: 0 Firma problema: P1: g.proj.exe P2: 8.4.0.0 P3: 67c1b293 P4: MSVCP140.dll P5: 14.32.31332.0 P6: 8b64702c P7: c0000005 P8: 00000000000132f8 P9: P10: File allegati: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC70B.tmp.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC8A2.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC8E2.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC8F0.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC95E.tmp.txt I file potrebbero essere disponibili qui: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_g.proj.exe_51b5231a2a1ea5f8fad13b8b77e9efc5d294dcb_7a926d0c_6b372199-67e8-4d0c-bfbf-da8a25888f2f Simbolo analisi: Nuova ricerca di soluzioni: 0 ID rapporto: a8036716-e21d-46f7-9d3e-2b79d6dea9cc Stato rapporto: 268435456 Bucket con hash: c73ca389f36d194801b06d2b958bdce3 GUID CAB: 0 It looks like the GRASS modules are using MSVCP140.dll available in C:\WINDOWS\SYSTEM32\ instead of the one available in C:\OSGeo4W\bin. The issue didn't occur running QGIS 3.34.11 with GRASS 8.4.0-2 on the same system. |
|||
See also: TracQuery, TracTickets, TracReports
