Edgewall Software

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: 21 [[TicketQuery(status=new&milestone=,count)]]
Number of new tickets: 1059 [[TicketQuery(status=new,count)]]
Number of reopened tickets: 3 [[TicketQuery(status=reopened,count)]]
Number of assigned tickets: 20 [[TicketQuery(status=assigned,count)]]
Number of invalid tickets: 1517 [[TicketQuery(status=closed,resolution=invalid,count)]]
Number of worksforme tickets: 1415 [[TicketQuery(status=closed,resolution=worksforme,count)]]
Number of duplicate tickets: 2185 [[TicketQuery(status=closed,resolution=duplicate,count)]]
Number of wontfix tickets: 990 [[TicketQuery(status=closed,resolution=wontfix,count)]]
Number of fixed tickets: 4509 [[TicketQuery(status=closed,resolution=fixed,count)]]
Number of untriaged tickets (milestone unset): 23 [[TicketQuery(status!=closed,milestone=,count)]]
Total number of tickets: 12285 [[TicketQuery(count)]]
Number of tickets reported or owned by current user: 1843 [[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: #12188, #1477, #493 [[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 anonymous
Summary Add a new project summary module.

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:

#181, #204, #226, #239, #351, #413, #450, #475, #519, #529

Format: count

[[TicketQuery(version=0.6|0.7&resolution=duplicate, count)]]

This is displayed as:

10

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:

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

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#13505 fixed Trac dies with segmentation fault in Python 3.11.0 Jun Omae seino
Description

In existence Trac environments /path/to/tracenv, tracd dies with segmentation fault.

$ python3 --version
Python 3.11.0
$ cd /path/to/tracenv
$ tracd -p 8000 .
Server starting in PID 2152.
Serving on 0.0.0.0:8000 view at http://127.0.0.1:8000/
Using HTTP/1.1 protocol version
127.0.0.1 - - [26/Nov/2022 09:53:15] "GET / HTTP/1.1" 200 -
Segmentation fault (core dumped)
$ 

I use:

  • Trac 1.5.4.dev0 (revision 17604)
  • Jinja2 3.1.2
  • Babel 2.11.0
  • MarkupSafe 2.1.1
  • Fedora 37 (both of x86_64 and aarch64)
#13504 cantfix Intertrac doesn't work from sub-level wiki pages only from tickets and top-level wiki pages geert.linders@…
Description

I have a server with several trac instances. If I add an Intertrac link to a ticket or top-level wiki page, it works fine. If I add the exact same link to a sub-level wiki page, it doesn't work. I am using Trac version 1.4.3.

The set-up in trac.ini is (this is common to all trac instances):

[intertrac]
development.title = New Product Development project
development.url = ../../development
maintenance.title = Maintenance project
maintenance.url = ../../maintenance
sandbox.title = Sandbox project
sandbox.url = ../../sandbox
administration.title = Server Administration project
administration.url = ../../administration

My sites are accessed as: http://trac/development, http://trac/maintenance, http://trac/sandbox and http://trac/administration.

If I add link [[maintenance:ticket:29|29]] to a ticket, it takes me to this ticket in the other Trac instance.

If I add the exact same link to a top-level wiki page, it works fine as well.

A top-level wiki page is for instance http://trac/development/wiki/BuildSystem or http://trac/development/wiki/WikiStart.

If I add the exact same link to a sub-level wiki page, it doesn't work and I get error: No handler matched request to /maintenance/intertrac/ticket:29.

A sub-level wiki page is for instance http://trac/development/wiki/BuildSystem/Makefiles.

How can I make the Intertrac links work from all wiki pages?

#13496 duplicate Uploading an attachment fails with "AssertionError: write() before start_response()" anonymous
Description

When adding an attachment to a wiki page (or just clicking the cancel button on the Add Attachment page) I get the error below in the browser (and in the Apache error log). No attachment is saved or added to the wiki page.

Trac version: 1.5.4dev from the trunk at revision 17603

OS: Fedora Server 34

Python version: 3.9.4

Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/trac/web/_fcgi.py", line 572, in run
    protocolStatus, appStatus = self.server.handler(self)
  File "/usr/local/lib/python3.9/site-packages/trac/web/_fcgi.py", line 1250, in handler
    write(b'') # in case body was empty
  File "/usr/local/lib/python3.9/site-packages/trac/web/_fcgi.py", line 1203, in write
    assert headers_set, 'write() before start_response()'
AssertionError: write() before start_response()
1 2 3 4 5 6 7 8 9 10 11


See also: TracQuery, TracTickets, TracReports

Last modified 9 months ago Last modified on Mar 6, 2022, 8:38:39 AM
Note: See TracWiki for help on using the wiki.