Trac Ticket Queries

In addition to reports, Trac provides support for custom ticket queries, used to display lists of tickets meeting a specified set of criteria.

To configure and execute a custom query, switch to the View Tickets module from the navigation bar, and select the Custom Query link.


When you first go to the query page the default filter will display tickets relevant to you:

  • If logged in then all open tickets it will display open tickets assigned to you.
  • If not logged in but you have specified a name or email address in the preferences then it will display all open tickets where your email (or name if email not defined) is in the CC list.
  • If not logged and no name/email defined in the preferences then all open issues are displayed.

Current filters can be removed by clicking the button to the left with the minus sign on the label. New filters are added from the pulldown lists at the bottom corners of the filters box ('And' conditions on the left, 'Or' conditions on the right). Filters with either a text box or a pulldown menu of options can be added multiple times to perform an or of the criteria.

You can use the fields just below the filters box to group the results based on a field, or display the full description for each ticket.

Once you've edited your filters click the Update button to refresh your results.

Clicking on one of the query results will take you to that ticket. You can navigate through the results by clicking the Next Ticket or Previous Ticket links just below the main menu bar, or click the Back to Query link to return to the query page.

You can safely edit any of the tickets and continue to navigate through the results using the Next/Previous/Back to Query links after saving your results. When you return to the query any tickets which were edited will be displayed with italicized text. If one of the tickets was edited such that it no longer matches the query criteria the text will also be greyed. Lastly, if a new ticket matching the query criteria has been created, it will be shown in bold.

The query results can be refreshed and cleared of these status indicators by clicking the Update button again.

Saving Queries

Trac allows you to save the query as a named query accessible from the reports module. To save a query ensure that you have Updated the view and then click the Save query button displayed beneath the results. You can also save references to queries in Wiki content, as described below.

Note: one way to easily build queries like the ones below, you can build and test the queries in the Custom report module and when ready - click Save query. This will build the query string for you. All you need to do is remove the extra line breaks.

Note: you must have the REPORT_CREATE permission in order to save queries to the list of default reports. The Save query button will only appear if you are logged in as a user that has been granted this permission. If your account does not have permission to create reports, you can still use the methods below to save a query.

You may want to save some queries so that you can come back to them later. You can do this by making a link to the query from any Wiki page.

[query:status=new|assigned|reopened&version=1.0 Active tickets against 1.0]

Which is displayed as:

Active tickets against 1.0

This uses a very simple query language to specify the criteria (see Query Language).

Alternatively, you can copy the query string of a query and paste that into the Wiki link, including the leading ? character:

[query:?status=new&status=assigned&status=reopened&group=owner Assigned tickets by owner]

Which is displayed as:

Assigned tickets by owner

Using the [[TicketQuery]] Macro

The TicketQuery macro lets you display lists of tickets matching certain criteria anywhere you can use WikiFormatting.



This is displayed as:

Keine Ergebnisse

Just like the query: wiki links, the parameter of this macro expects a query string formatted according to the rules of the simple ticket query language. This also allows displaying the link and description of a single ticket:


This is displayed as:

W900V/7170 Alien Image / Gaming Patch

A more compact representation without the ticket summaries is also available:

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

This is displayed as:

Keine Ergebnisse

Finally, if you wish to receive only the number of defects that match the query, use the count parameter.

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

This is displayed as:


Customizing the table format

You can also customize the columns displayed in the table format (format=table) by using col≤field> - you can specify multiple fields and what order they are displayed by placing pipes (|) between the columns like below:


This is displayed as:

Ergebnisse (1 - 3 von 2649)

1 2 3 4 5 6 7 8 9 10 11
Ticket Lösung Zusammenfassung Verantwortlicher Ersteller
#2950 fixed Fehler in uclibcxx Patch: 101-wrapper_proper_parameter_passing.freetz.uclibcxx.patch er13 f_666
#2945 fixed curl-7.56.1 -> 7.57.0 f_666
#2944 worksforme Boot bleibt im Bereich OpenVPN hängen ThiloG
1 2 3 4 5 6 7 8 9 10 11

Full rows

In table format you can also have full rows by using rows≤field> like below:


This is displayed as:

Ergebnisse (1 - 3 von 2649)

1 2 3 4 5 6 7 8 9 10 11
Ticket Lösung Zusammenfassung Verantwortlicher Ersteller
#2950 fixed Fehler in uclibcxx Patch: 101-wrapper_proper_parameter_passing.freetz.uclibcxx.patch er13 f_666

Der Patch 101 für die uclibcxx patcht folgenden Kode in den g++ Wrapper:

$(Q)echo '[ -n "$$V" ] && [ $$V -gt 1 ] && \\' >> $@.tmp                                                                                                                                          
$(Q)echo '      echo $(strip $(CXX) $(GEN_CFLAGS) $(GEN_CXXFLAGS) $(EH_CXXFLAGS)) $$WRAPPER_INCLUDEDIR "$$@" $$WRAPPER_LIBS_OPTIONS >&2' >> $@.tmp                                               
$(Q)echo '      exec $(strip $(CXX) $(GEN_CFLAGS) $(GEN_CXXFLAGS) $(EH_CXXFLAGS)) $$WRAPPER_INCLUDEDIR "$$@" $$WRAPPER_LIBS_OPTIONS' >> $@.tmp

Das ergibt diese Fehlermeldung, zumindest mit der Bash 4.4.12:

/bin/g++-uc: Zeile 16: \: Kommando nicht gefunden

Hat in der Praxis nur kosmetische Auswirkungen, ist aber trotzdem unschön. Der angehängte Patch entfernt einen Backslash.

#2945 fixed curl-7.56.1 -> 7.57.0 f_666

Fixed in 7.57.0 - November 29 2017


auth: add support for RFC7616 - HTTP Digest access authentication share: add support for sharing the connection cache HTTP: implement Brotli content encoding


CVE-2017-8816: NTLM buffer overflow via integer overflow CVE-2017-8817: FTP wildcard out of bounds read CVE-2017-8818: SSL out of buffer access curl_mime_filedata.3: fix typos libtest: Add required test libraries for lib1552 and lib1553 fix time diffs for systems using unsigned time_t ftplistparser: memory leak fix: free temporary memory always multi: allow table handle sizes to be overridden wildcards: don't use with non-supported protocols curl_fnmatch: return error on illegal wildcard pattern transfer: Fix chunked-encoding upload too early exit curl_setup: Improve detection of CURL_WINDOWS_APP resolvers: only include anything if needed setopt: fix CURLOPT_SSH_AUTH_TYPES option read appveyor: add a win32 build Curl_timeleft: change return type to timediff_t cmake: Export libcurl and curl targets to use by other cmake projects curl: in -F option arg, comma is a delimiter for files only curl: improved ";type=" handling in -F option arguments timeval: use mach_absolute_time() on MacOS curlx: the timeval functions are no longer provided as curlx_* do not generate comment with current date memdebug: use send/recv signature for curl_dosend/curl_dorecv cookie: avoid NULL dereference url: fix CURLOPT_POSTFIELDSIZE arg value check to allow -1 include: remove conncache.h inclusion from where its not needed CURLOPT_MAXREDIRS: allow -1 as a value tests: Fixed torture tests on tests 556 and 650 http2: Fixed OOM handling in upgrade request url: fix CURLOPT_DNS_CACHE_TIMEOUT arg value check to allow -1 CURLOPT_INFILESIZE: accept -1 curl: pass through [] in URLs instead of calling globbing error curl: speed up handling of many URLs ntlm: avoid malloc(0) for zero length passwords url: remove faulty arg value check from CURLOPT_SSH_AUTH_TYPES HTTP: support multiple Content-Encodings travis: add a job with brotli enabled url: remove unncessary NULL-check fnmatch: remove dead code connect: store IPv6 connection status after valid connection imap: deal with commands case insensitively —interface: add support for Linux VRF content_encoding: fix inflate_stream for no bytes available cmake: Correctly include curl.rc in Windows builds cmake: Add missing setmode check connect.c: remove executable bit on file SMB: fix uninitialized local variable zlib/brotli: only include header files in modules needing them URL: return error on malformed URLs with junk after IPv6 bracket openssl: fix too broad use of HAVE_OPAQUE_EVP_PKEY macOS: Fix missing connectx function with Xcode version older than 9.0 —resolve: allow IP address within [] brackets examples/curlx: Fix code style ntlm: remove unnecessary NULL-check to please scan-build Curl_llist_remove: fix potential NULL pointer deref mime: fix "Value stored to 'sz' is never read" scan-build error openssl: fix "Value stored to 'rc' is never read" scan-build error http2: fix "Value stored to 'hdbuf' is never read" scan-build error http2: fix "Value stored to 'end' is never read" scan-build error Curl_open: fix OOM return error correctly url: reject ASCII control characters and space in host names examples/rtsp: clear RANGE again after use connect: improve the bind error message make: fix "make distclean" connect: add support for new TCP Fast Open API on Linux metalink: fix memory-leak and NULL pointer dereference URL: update "file:" URL handling ssh: remove check for a NULL pointer global_init: ignore CURL_GLOBAL_SSL's absense

#2944 worksforme Boot bleibt im Bereich OpenVPN hängen ThiloG


meine 7490 bleibt während des bootens in deen freetz openvpn skripten hängen.

Dieses Problem besteht schon länger. (mind. seit 6.83)

Ich nutze hier ein OpenVPN-Setup mit eigener Konfig.

mod-log sieht so aus:

rc.mod version freetz-devel-14560 crond is disabled. Starting AVM telnetd … done. Starting Freetz webinterface … done. swap is disabled. syslogd is disabled. downloader is disabled. Starting inetd … done. Setting up SSH authorized_keys for root … done. Starting dropbear SSH server … done. rm: remove '/mod/etc/default.openvpn/openvpn_conf'?

in der Prozessliste stehen bis ultimo:

3941 root 1412 S {rc.openvpn} /bin/sh /etc/init.d/rc.openvpn 3948 root 1388 S {generate_virtua} /bin/sh /mod/etc/default.openvpn/generate_virtual_pkg OpenVPN 3953 root 1388 S {generate_virtua} /bin/sh /mod/etc/default.openvpn/generate_virtual_pkg OpenVPN

nach killen von Prozess 3948

gehts im mod-log weiter

rm: remove '/mod/etc/default.openvpn/openvpn_conf'? Terminated Starting openvpn … done. stunnel is disabled. Setting up onlinechanged scripting … done. Starting RRDstats … done. rrdstats (webcfg-one) is updating inetd … inactive. rrdstats (webcfg-rrd) is updating inetd … inactive.

und das restliche Bootprozedere läuft durch.

1 2 3 4 5 6 7 8 9 10 11

Query Language

query: TracLinks and the [[TicketQuery]] macro both use a mini “query language” for specifying query filters. Basically, the filters are separated by ampersands (&). Each filter then consists of the ticket field name, an operator, and one or more values. More than one value are separated by a pipe (|), meaning that the filter matches any of the values. To include a literal & or | in a value, escape the character with a backslash (\).

The available operators are:

= the field content exactly matches one of the values
~= the field content contains one or more of the values
^= the field content starts with one of the values
$= the field content ends with one of the values

All of these operators can also be negated:

!= the field content matches none of the values
!~= the field content does not contain any of the values
!^= the field content does not start with any of the values
!$= the field content does not end with any of the values

The date fields created and modified can be constrained by using the = operator and specifying a value containing two dates separated by two dots (..). Either end of the date range can be left empty, meaning that the corresponding end of the range is open. The date parser understands a few natural date specifications like "3 weeks ago", "last month" and "now", as well as Bugzilla-style date specifications like "1d", "2w", "3m" or "4y" for 1 day, 2 weeks, 3 months and 4 years, respectively. Spaces in date specifications can be left out to avoid having to quote the query string.

created=2007-01-01..2008-01-01 query tickets created in 2007
created=lastmonth..thismonth query tickets created during the previous month
modified=1weekago.. query tickets that have been modified in the last week
modified=..30daysago query tickets that have been inactive for the last 30 days

See also: TracTickets, TracReports, TracGuide

zuletzt geändert vor 5 Jahren Zuletzt geändert am 03.11.2012 15:44:22