This page documents the 1.4 (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: | 22 | [[TicketQuery(status=new&milestone=,count)]]
|
| Number of new tickets: | 1062 | [[TicketQuery(status=new,count)]]
|
| Number of reopened tickets: | 4 | [[TicketQuery(status=reopened,count)]]
|
| Number of assigned tickets: | 22 | [[TicketQuery(status=assigned,count)]]
|
| Number of invalid tickets: | 1514 | [[TicketQuery(status=closed,resolution=invalid,count)]]
|
| Number of worksforme tickets: | 1420 | [[TicketQuery(status=closed,resolution=worksforme,count)]]
|
| Number of duplicate tickets: | 2192 | [[TicketQuery(status=closed,resolution=duplicate,count)]]
|
| Number of wontfix tickets: | 994 | [[TicketQuery(status=closed,resolution=wontfix,count)]]
|
| Number of fixed tickets: | 4575 | [[TicketQuery(status=closed,resolution=fixed,count)]]
|
| Number of untriaged tickets (milestone unset): | 24 | [[TicketQuery(status!=closed,milestone=,count)]]
|
| Total number of tickets: | 12379 | [[TicketQuery(count)]]
|
| Number of tickets reported or owned by current user: | 1851 | [[TicketQuery(reporter=$USER,or,owner=$USER,count)]]
|
| Number of tickets created this month: | 5 | [[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: | #13784, #13783, #13782 | [[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 11291)
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 11291)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #13782 | cantfix | $.datepicker is undefined | ||
| Description |
Firefox 115.13.0esr (64-bit) javascript console prints: Trac version is 1.6 with python-3.9 jQuery.Deferred exception: $.datepicker is undefined @https://trac.osgeo.org/osgeo/chrome/common/js/jquery-ui-i18n.js:5:3 e@xxx/chrome/common/js/jquery.js:2:30310 Deferred/then/l/</t<@xxx/chrome/common/js/jquery.js:2:30612 setTimeout handler*Deferred/then/l/<@xxx/chrome/common/js/jquery.js:2:30821 c@xxx/chrome/common/js/jquery.js:2:28599 fireWith@xxx/chrome/common/js/jquery.js:2:29344 fire@xxx/chrome/common/js/jquery.js:2:29380 c@xxx/chrome/common/js/jquery.js:2:28599 fireWith@xxx/chrome/common/js/jquery.js:2:29344 ready@xxxx/chrome/common/js/jquery.js:2:32317 $@xxx/chrome/common/js/jquery.js:2:32096 EventListener.handleEvent*@xxx/chrome/common/js/jquery.js:2:32465 @xxx/chrome/common/js/jquery.js:2:220 @xxx/chrome/common/js/jquery.js:2:225 undefined jquery.js:2:31865 NOTE: I had to replace http links with some xxx to avoid the antispam measure (too many external links) |
|||
| #13781 | cantfix | empty rcpt TO with 1.4.4 on python2.7 (send: 'rcpt TO:<>\r\n') | ||
| Description |
a trac instance of mine was running in version 1.2.2 for quite some time and worked flawlessly along email2trac. It's hosted at uberspace and it used to run on python2.6 On 2024-07-25 they swapped /usr/bin/python to point to python2.7 and my mail issues began.
During my debug journey I upgraded to trac 1.4.4 but when trac wants to send mails (on ticket updates) I get
So I added 622 server.set_debuglevel(1) to "python2.7/site-packages/trac/notification/mail.py" and can now see the smtp dialog which is: reply: '235 Authentication succeeded\r\n' reply: retcode (235); Msg: Authentication succeeded send: 'mail FROM:<sender@mymail.com> size=1697\r\n' reply: '250 Requested mail action okay, completed\r\n' reply: retcode (250); Msg: Requested mail action okay, completed send: 'rcpt TO:<>\r\n' reply: '501 Syntax error in parameters or arguments\r\n' reply: retcode (501); Msg: Syntax error in parameters or arguments send: 'rcpt TO:<>\r\n' reply: '501 Syntax error in parameters or arguments\r\n' reply: retcode (501); Msg: Syntax error in parameters or arguments send: 'rcpt TO:<>\r\n' reply: '501 Syntax error in parameters or arguments\r\n' reply: retcode (501); Msg: Syntax error in parameters or arguments send: 'rset\r\n' reply: '250 OK\r\n' I have proof that the mailing of this instance worked fine with the previus version of uberspace's python and my trac 1.2.2 mid-july. We recognized the lack of mails Mid-August and because of lrwxrwxrwx. 1 root root 7 25. Jul 19:34 /usr/bin/python -> python2
my guess is, that it's connected to the swap of the python link.
Unfortunately there is no more python2.6 left on the box which seems to run on If I remember correctly, 1.2.2 and python27 had the issue with an empty 'from' field in the smtp dialog send: 'mail FROM:<> size=1697\r\n'
causing |
|||
| #13779 | duplicate | Load environment variables in config file | ||
| Description |
Hi, We're deploying trac in a containerized environment and it would be useful to pass parts of the configuration file as environment variables, specifically the db string / db credentials. I've found prior art doing this:
( with information about why the change here: https://github.com/marina-lab/docker-trac/commit/054a2d820856abc8d7b78a727a4c706f9917332d#diff-7f3552a4131e0f60dfffa919511f1660ab995c4c9c92ef10591c9003033fbfb5). The attached patch allows for embedding eg %(DATABASE_URL)s in the config file using configparser's machinery. |
|||
See also: TracQuery, TracTickets, TracReports
