Version 1 (modified by trac, 8 years ago) (diff)


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.

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:

No results

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.

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

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

This is displayed as:

No results

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:

Results (1 - 3 of 5987)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#7964 duplicate Compile error jworrall
#7960 fixed Trying to encode to AV1 results in "g_threads out of range [..64]" error cyrozap
#7959 fixed Typo in tinterlace doc section in filters.texi Gyan laurfb
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:

Results (1 - 3 of 5987)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#7964 duplicate Compile error jworrall

Summary of the bug: Compilation fails with gmake (make doesn't work on my system, but I've built it this way on this system as recently as March). It gets about 15 minutes in before the Error:

. . .
CC	libavcodec/ptx.o
CC	libavcodec/qcelpdec.o
HOSTCC	libavcodec/qdm2_tablegen.o
In file included from libavcodec/qdm2_tablegen.c:24:
In file included from libavcodec/tableprint_vlc.h:43:
libavcodec/bitstream.c:231:17: warning: implicit declaration of function 'avpriv_request_sample' is
      invalid in C99 [-Wimplicit-function-declaration]
                avpriv_request_sample(NULL, "strange codes");
1 warning generated.
HOSTLD	libavcodec/qdm2_tablegen
libavcodec/qdm2_tablegen.o: In function `build_table':
qdm2_tablegen.c:(.text+0x1b7e): undefined reference to `avpriv_request_sample'
clang: error: linker command failed with exit code 1 (use -v to see invocation)
gmake: *** [ffbuild/common.mak:155: libavcodec/qdm2_tablegen] Error 1

How to reproduce:

[root@ffmpeg /usr/local/build/ffmpeg]# ./configure --cc=/usr/bin/clang \
--pkg-config-flags="--static" --enable-static --disable-shared \
--enable-nonfree --enable-gpl --enable-version3 \
--enable-hardcoded-tables --enable-libfdk-aac --enable-libx264 \
--enable-libx265 --enable-avfilter --enable-filters \
--disable-outdevs --disable-network --enable-libfreetype \
--enable-libfontconfig --enable-libfribidi
install prefix            /usr/local
source path               .
C compiler                /usr/bin/clang
C library                 
ARCH                      x86 (generic)
big-endian                no
runtime cpu detection     yes
standalone assembly       yes
x86 assembler             nasm
MMX enabled               yes
MMXEXT enabled            yes
3DNow! enabled            yes
3DNow! extended enabled   yes
SSE enabled               yes
SSSE3 enabled             yes
AESNI enabled             yes
AVX enabled               yes
AVX2 enabled              yes
AVX-512 enabled           yes
XOP enabled               yes
FMA3 enabled              yes
FMA4 enabled              yes
i686 features enabled     yes
CMOV is fast              yes
EBX available             yes
EBP available             yes
debug symbols             yes
strip symbols             yes
optimize for size         no
optimizations             yes
static                    yes
shared                    no
postprocessing support    yes
network support           no
threading support         pthreads
safe bitstream reader     yes
texi2html enabled         no
perl enabled              yes
pod2man enabled           yes
makeinfo enabled          no
makeinfo supports HTML    no
. . . 
[root@ffmpeg /usr/local/build/ffmpeg]# gmake

ffmpeg version Can't find a version but just git-cloned it this morning

#7960 fixed Trying to encode to AV1 results in "g_threads out of range [..64]" error cyrozap

On FFmpeg version 4.1.3 (as distributed by Debian), on a system with 144 CPU threads, trying to encode any media as AV1 fails with the message "[libaom-av1 @ 0x137013140] Additional information: g_threads out of range [..64]". I've attached the verbose log if you'd like to see it.

It seems this has already been fixed in this commit, but that patch is only in git master, so the issue still exists in the stable version.

Would it be possible for this patch to be applied to the 4.1 branch?

Also, other than building FFmpeg myself, is there any way I can work around this issue? e.g., is there a "limit max CPUs" option I can set somewhere?

#7959 fixed Typo in tinterlace doc section in filters.texi Gyan laurfb

Summary of the bug:

  1. Line 17169 - "@item low_pass_filter, vlfp". Correct "vlpf" instead of "vlfp"
  2. Line 17176 - "@item complex_filter, cvlfp". Correct "cvlpf" instead of "cvlfp"

regards, laur

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