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:

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. This also allows displaying the link and description of a single ticket:


This is displayed as:

Fuzzed sample crashes ffplay

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

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#7608 duplicate Add opencv 4 support Ilya87
#7606 invalid ffmpeg 4.0.2 and above missing 'ffio_open_dyn_packet_buf' from avformat.lib & avformat.dll dinesh.gupta01
#7605 invalid Native opus decoder does not remove padding at start jchennales
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 5705)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#7608 duplicate Add opencv 4 support Ilya87

Summary of the bug: 1 - pkg-config file for opencv 4 has name opencv4.pc 2 - even I create a symlink to opencv.pc compilation fails - opencv 4 doesn't have cxcore.h header: fatal error: opencv/cxcore.h: No such file or directory

#include <opencv/cxcore.h>

How to reproduce:

./configure --enable-libopencv
ffmpeg version git-master
built on AntergOS x86_64

Patches should be submitted to the ffmpeg-devel mailing list and not this bug tracker.

#7606 invalid ffmpeg 4.0.2 and above missing 'ffio_open_dyn_packet_buf' from avformat.lib & avformat.dll dinesh.gupta01

While building 'ffmpeg' 4.0.2 and above, missing function 'ffio_open_dyn_packet_buf'. Due to this I am unable to compile my project. I spend my whole week to find the solution but didn't get success. When searching this function in code than it is available on source code.But when build from sorce code this function is missing. Please guide me what I need to do.

./libavformat/aviobuf.c:1396:int ffio_open_dyn_packet_buf(AVIOContext s, int max_packet_size) ./libavformat/avio_internal.h:120:int ffio_open_dyn_packet_buf(AVIOContext s, int max_packet_size); ./libavformat/movenchint.c:430: if ((ret = ffio_open_dyn_packet_buf(&rtp_ctx->pb, ./libavformat/rtpenc_chain.c:85: ret = ffio_open_dyn_packet_buf(&rtpctx->pb, packet_size); ./libavformat/rtspenc.c:158: * ffio_open_dyn_packet_buf. So by writing the interleaving header ./libavformat/rtspenc.c:178: return ffio_open_dyn_packet_buf(&rtpctx->pb, RTSP_TCP_MAX_PACKET_SIZE);

I have below environment: OS : Windows 10 MSVC : Visual Studio 15 with Windows SDK 10.0.17763.0 MSYS2 : MINGW32_NT-10.0-WOW

Getting below error:

server-ffmpeg.obj : error LNK2019: unresolved external symbol _ffio_open_dyn_packet_buf referenced in function "int cdecl ff_server_send_packet_1(char const *,void *,int,struct AVPacket *,int64,struct timeval *)" (?ff_server_send_packet_1@@YAHPBDPAXHPAUAVPacket@@_JPAUtimeval@@@Z)

rtspserver.obj : error LNK2019: unresolved external symbol _ff_rtsp_parse_line referenced in function "void * cdecl rtspserver(void *)" (?rtspserver@@YAPAXPAX@Z) server-ffmpeg.dll : fatal error LNK1120: 1 unresolved externals

Please guild me to achieve above result.


#7605 invalid Native opus decoder does not remove padding at start jchennales

Summary of the bug:

The native opus decoder does not remove padding at start of file

How to reproduce:

Using a 10s mono 44k sine wave wav file split in two. The files are encoded as opus and then decoded back to wav. When using the native (default) decoder the second file has a clear silence at the beginning which results in an audible glitch if played right after the first file. When forcing libopus as the decoded this does not happen and the files join perfectly (albeit some understandable encoding artifacts at the split point)

ffmpeg -i sine01.wav -vn -c:a libopus -b:a 64k -vbr on -compression_level 10 sine01.opus.ogg
ffmpeg -i sine02.wav -vn -c:a libopus -b:a 64k -vbr on -compression_level 10 sine02.opus.ogg
ffmpeg -i sine01.opus.ogg sine01.deopus.wav
ffmpeg -i sine02.opus.ogg sine02.deopus.wav

ffmpeg -c:a libopus -i sine01.opus.ogg sine01.deopus_libopus.wav
ffmpeg -c:a libopus -i sine02.opus.ogg sine02.deopus_libopus.wav

ffmpeg version 4.1 Copyright (c) 2000-2018 the FFmpeg developers
  built with gcc 8.2.1 (GCC) 20181017
  configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libtheora --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab --enable-libvorbis --enable-libvo-amrwbenc --enable-libmysofa --enable-libspeex --enable-libxvid --enable-libaom --enable-libmfx --enable-amf --enable-ffnvcodec --enable-cuvid --enable-d3d11va --enable-nvenc --enable-nvdec --enable-dxva2 --enable-avisynth
  libavutil      56. 22.100 / 56. 22.100
  libavcodec     58. 35.100 / 58. 35.100
  libavformat    58. 20.100 / 58. 20.100
  libavdevice    58.  5.100 / 58.  5.100
  libavfilter     7. 40.101 /  7. 40.101
  libswscale      5.  3.100 /  5.  3.100
  libswresample   3.  3.100 /  3.  3.100
  libpostproc    55.  3.100 / 55.  3.100
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

Last modified 3 years ago Last modified on Jul 6, 2015, 10:44:56 PM