Trac Ticket Queries

In addition to reports, Trac provides support for custom ticket queries, which can be used to display tickets that meet specified criteria.

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

Filters

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 in and no name/email is 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 on 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.

After you have edited your filters, click the Update button to refresh your results.

Navigating Tickets

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.

Using TracLinks

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

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

1 2 3 4 5 6 7 8 9 10 11 →

Ticket	Resolution	Summary	Owner	Reporter
#3604	Fixed	Fix log level tweaks from logging.conf		seblu
#3602	Fixed	Add torrent dialog removes directory from file tree	bro	bro
#3600	Fixed	Fail to run using python 3.11		th0ma7

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>:

[[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 2448)

1 2 3 4 5 6 7 8 9 10 11 →

Ticket	Resolution	Summary	Owner	Reporter
#3604	Fixed	Fix log level tweaks from logging.conf		seblu
Description	When you set a config directory path (-c) on the command line, and only when, a file named logging.conf is read to set fine grained log levels. This allows to have per module/plugin log levels. The file is parsed and the log levels are set in the deluge.log.tweak_logging_levels. This function set the appropriate logger to the desired level. Despite the log level is changed, log levels less than ERROR are still not logged. The reason is that the log level check is done twice, in the logging.Logger class and in the logging.Handler class. Fix proposed: ​https://github.com/deluge-torrent/deluge/pull/428
#3602	Fixed	Add torrent dialog removes directory from file tree	bro	bro
Description	When adding a torrent that contains one directory with one file inside, the directory is not included in the tree view. This has been the behavior since the dawn of time, presumable due to the mistaken beleif that the directory was not needed. All other torrent clients include the directory even if there is only one file inside
#3600	Fixed	Fail to run using python 3.11		th0ma7
Description	Maintainer of the SynoCommunity? deluge package. Currently runs really well using version 2.1.1 on python 3.10. Tried updating to python 3.11 but got the following error: th0ma7@th0ma7-nas:/var/packages/deluge/var$ cat deluge.log Sat May 13 09:58:18 EDT 2023 Starting deluge command /volume1/@appstore/deluge/env/bin/deluged -c /volume1/@appdata/deluge -l /volume1/@appdata/deluge/logs/deluged.log -L info --logrotate -P /volume1/@appdata/deluge/logs/deluged.pid -d Starting deluge command /volume1/@appstore/deluge/env/bin/deluge-web -c /volume1/@appdata/deluge -l /volume1/@appdata/deluge/logs/deluge-web.log -L info --logrotate -P /volume1/@appdata/deluge/logs/deluge-web.pid -d Traceback (most recent call last): File "/volume1/@appstore/deluge/env/lib/python3.11/site-packages/deluge/_libtorrent.py", line 21, in <module> import deluge.libtorrent as lt ModuleNotFoundError: No module named 'deluge.libtorrent' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/volume1/@appstore/deluge/env/bin/deluged", line 8, in <module> sys.exit(start_daemon()) ^^^^^^^^^^^^^^ File "/volume1/@appstore/deluge/env/lib/python3.11/site-packages/deluge/core/daemon_entry.py", line 81, in start_daemon parser = ArgParserBase() ^^^^^^^^^^^^^^^ File "/volume1/@appstore/deluge/env/lib/python3.11/site-packages/deluge/argparserbase.py", line 178, in __init__ version='%(prog)s ' + _get_version_detail(), ^^^^^^^^^^^^^^^^^^^^^ File "/volume1/@appstore/deluge/env/lib/python3.11/site-packages/deluge/argparserbase.py", line 89, in _get_version_detail from deluge._libtorrent import LT_VERSION File "/volume1/@appstore/deluge/env/lib/python3.11/site-packages/deluge/_libtorrent.py", line 24, in <module> import libtorrent as lt SystemError: type Boost.Python.enum has the Py_TPFLAGS_HAVE_GC flag but has no traverse function Traceback (most recent call last): File "/volume1/@appstore/deluge/env/lib/python3.11/site-packages/deluge/_libtorrent.py", line 21, in <module> import deluge.libtorrent as lt ModuleNotFoundError: No module named 'deluge.libtorrent' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/volume1/@appstore/deluge/env/bin/deluge-web", line 8, in <module> sys.exit(start()) ^^^^^^^ File "/volume1/@appstore/deluge/env/lib/python3.11/site-packages/deluge/ui/web/__init__.py", line 5, in start web = Web() ^^^^^ File "/volume1/@appstore/deluge/env/lib/python3.11/site-packages/deluge/ui/web/web.py", line 24, in __init__ super().__init__( File "/volume1/@appstore/deluge/env/lib/python3.11/site-packages/deluge/ui/ui.py", line 40, in __init__ self.__parser = ArgParserBase(**kwargs) ^^^^^^^^^^^^^^^^^^^^^^^ File "/volume1/@appstore/deluge/env/lib/python3.11/site-packages/deluge/argparserbase.py", line 178, in __init__ version='%(prog)s ' + _get_version_detail(), ^^^^^^^^^^^^^^^^^^^^^ File "/volume1/@appstore/deluge/env/lib/python3.11/site-packages/deluge/argparserbase.py", line 89, in _get_version_detail from deluge._libtorrent import LT_VERSION File "/volume1/@appstore/deluge/env/lib/python3.11/site-packages/deluge/_libtorrent.py", line 24, in <module> import libtorrent as lt SystemError: type Boost.Python.enum has the Py_TPFLAGS_HAVE_GC flag but has no traverse function

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. Filters are separated by ampersands (&). Each filter 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 omitted 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, TicketQuery