This page documents the 1.6 (latest stable) release. Documentation for other releases can be found here.
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: | 31 | [[TicketQuery(status=new&milestone=,count)]]
|
| Number of new tickets: | 1074 | [[TicketQuery(status=new,count)]]
|
| Number of reopened tickets: | 6 | [[TicketQuery(status=reopened,count)]]
|
| Number of assigned tickets: | 26 | [[TicketQuery(status=assigned,count)]]
|
| Number of invalid tickets: | 1515 | [[TicketQuery(status=closed,resolution=invalid,count)]]
|
| Number of worksforme tickets: | 1421 | [[TicketQuery(status=closed,resolution=worksforme,count)]]
|
| Number of duplicate tickets: | 2194 | [[TicketQuery(status=closed,resolution=duplicate,count)]]
|
| Number of wontfix tickets: | 994 | [[TicketQuery(status=closed,resolution=wontfix,count)]]
|
| Number of fixed tickets: | 4621 | [[TicketQuery(status=closed,resolution=fixed,count)]]
|
| Number of untriaged tickets (milestone unset): | 35 | [[TicketQuery(status!=closed,milestone=,count)]]
|
| Total number of tickets: | 12446 | [[TicketQuery(count)]]
|
| Number of tickets reported or owned by current user: | 1853 | [[TicketQuery(reporter=$USER,or,owner=$USER,count)]]
|
| Number of tickets created this month: | 0 | [[TicketQuery(created=thismonth..,count)]]
|
| Number of closed Firefox tickets: | 13 | [[TicketQuery(status=closed,keywords~=firefox,count)]]
|
| Number of closed Opera tickets: | 12 | [[TicketQuery(status=closed,keywords~=opera,count)]]
|
| Number of closed tickets affecting Firefox and Opera: | 1 | [[TicketQuery(status=closed,keywords~=firefox opera,count)]]
|
| Number of closed tickets affecting Firefox or Opera: | 24 | [[TicketQuery(status=closed,keywords~=firefox|opera,count)]]
|
| Number of tickets that affect Firefox or are closed and affect Opera: | 25 | [[TicketQuery(status=closed,keywords~=opera,or,keywords~=firefox,count)]]
|
| Number of closed Firefox tickets that don't affect Opera: | 1 | [[TicketQuery(status=closed,keywords~=firefox -opera,count)]]
|
| Last 3 modified tickets: | #13911, #13915, #13914 | [[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:
- #181
- Wiki preview injects new lines
- #204
- request for colour legend (or something similar) for ticket groups in reports
- #226
- Ticket Dependencies
- #239
- Link to diff of specifik wiki change instead of the page itself
- #351
- All ticket modifications should be tracked in timeline
- #413
- Installing on Windows, drive other than C:
- #450
- Diffviewer should try to convert the text into utf-8.
- #475
- merging of similar tickets
- #519
- Python process sometimes hangs on Windows Server 2003
- #529
- IE 5-6 over HTTPS broken downloads
[[TicketQuery(id=123)]]
This is displayed as:
- #123
- No SQL error display
Format: compact
[[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]]
This is displayed as:
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
5 / 5
enhancement
2 / 2
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 11340)
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 11340)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #13914 | fixed | quick-jump search not working with diff: links | ||
| Description |
If you enter Note: The page displays a notice saying "You arrived here through the quick-jump search feature. To instead search for the term diff:@1:3, click here." If you follow that link then that page shows a quickjump link which works correctly. I've tested this on the 1.4 and 1.6 demo Trac's and they both have this problem. I have previously used this feature with Trac 1.0 when it worked as expected. |
|||
| #13912 | fixed | Message extraction fails with error no such option 'no-default-keywords' | ||
| Description |
extract task failing…. $ make python=310 extract python -Wdefault setup.py extract_messages extract_messages_js extract_messages_tracini running extract_messages ... writing PO template file to trac/locale/messages.pot running extract_messages_js error: error in setup.cfg: command 'extract_messages' has no such option 'no-default-keywords' make: *** [Makefile:208: extract] Error 1 $ ~/venv/py310/bin/python -Wignore setup.py extract_messages >/dev/null $ ~/venv/py310/bin/python -Wignore setup.py extract_messages_js >/dev/null error: error in setup.cfg: command 'extract_messages' has no such option 'no-default-keywords' $ ~/venv/py310/bin/python -Wignore setup.py extract_messages_tracini >/dev/null error: error in setup.cfg: command 'extract_messages' has no such option 'no-default-keywords' Babel 2.18.0 is used. jun66j5@localhost:1426$ ~/venv/py310/bin/pip show Babel Name: babel Version: 2.18.0 Summary: Internationalization utilities Home-page: https://babel.pocoo.org/ Author: Armin Ronacher Author-email: armin.ronacher@active-4.com License: BSD-3-Clause Location: /home/jun66j5/venv/py310/lib/python3.10/site-packages Requires: Required-by: |
|||
| #13910 | worksforme | Unable to upgrade from Trac 1.0.1 to Trac 1.6 | ||
| Description |
I'm trying to upgrade my Trac instance from 1.0.1 (yes!) to Trac 1.6. The upgrade instructions don't seem to suggest that this is not possible. When I attempt the upgrade, I get this error: rac-admin ./multics-trac upgrade
/Users/eswenson/src/trac/venv/lib/python3.14/site-packages/trac/__init__.py:14: UserWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html. The pkg_resources package is slated for removal as early as 2025-11-30. Refrain from using this package or pin to Setuptools<81.
from pkg_resources import DistributionNotFound, get_distribution
Error: Unable to check for upgrade of trac.db.api.DatabaseManager: UndefinedTable: relation "system" does not exist
LINE 2: SELECT value FROM "system" WHERE name='d...
^
I'm using a database setting like: postgres://multicstrac@localhost:5432/multics_trac?schema=trac
When I connect to the multics_trac database using psql, I can see the system table with |
|||
See also: TracQuery, TracTickets, TracReports
