This page documents the 0.11 release. Documentation for other releases can be found here.
Trac Ticket Queries
Table of Contents
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.
Filters
When you first go to the query page the default filters will display all open tickets, or if you're logged in it will display open tickets assigned to you. Current filters can be removed by clicking the button to the right with the minus sign on the label. New filters are added from the pulldown list in the bottom-right corner of the filters box. 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.
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
While Trac does not yet allow saving a named query and somehow making it available in a navigable list, you can save references to queries in Wiki content, as described below.
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:
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:
Using the [[TicketQuery]] Macro
The TicketQuery macro lets you display lists of tickets matching certain criteria anywhere you can use WikiFormatting.
Example:
[[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
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:
Finally if you wish to receive only the number of defects that match the query using 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:
[[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter)]]
This is displayed as:
Results (1 - 3 of 11341)
Full rows
In table format you can also have full rows by using rows≤field> like below:
[[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 11341)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #13917 | cantfix | trac 1.6 crashes after adding svn repository on python 3.13.0 | ||
| Description |
The system I am using it on is debian 13 (trixie). It uses python3. # python3 --version Python 3.13.5 # trac-admin --version trac-admin 1.6 Here are the steps I used to set it up: # apt-get install libapache2-mod-wsgi-py3 python3-pip python3-setuptools python3-genshi python3-subversion sqlite3 libsqlite3-dev # pip install --break-system-packages pysqlite3 && pip install --break-system-packages --upgrade pysqlite3 # pip --version pip 25.1.1 from /usr/lib/python3/dist-packages/pip (python 3.13) # pip install --break-system-packages babel docutils pygments textile && pip install --break-system-packages --upgrade babel docutils pygments textile # pip install --break-system-packages Trac && pip install --break-system-packages --upgrade Trac I setup a new project: # rm -rf /usr/share/trac/projects/test # mkdir -p /usr/share/trac/projects/test # trac-admin /usr/share/trac/projects/test initenv -set project name to test Copied over header-logo.jpg to /usr/share/trac/projects/test/htdocs set my user to be admin # trac-admin /usr/share/trac/projects/test permission add admin TRAC_ADMIN Edit /usr/share/trac/projects/test/conf/trac.ini -change this section to match [header_logo] alt = test height = 85 link = /trac src = site/header-logo.jpg width = 900 -change this section to match [trac] base_url = https://test.local/trac -change this section to match [trac] secure_cookies = enabled -add this as a new section [components] tracopt.versioncontrol.svn.* = enabled tracopt.perm.authz_policy.* = enabled -change this section to match putting AuthzPolicy in front [trac] permission_policies = AuthzPolicy, DefaultPermissionPolicy, LegacyAttachmentPolicy -add this as a new section [authz_policy] authz_file = /etc/apache2/testpermissions Then I edited the website configuration file for apache to have: WSGIScriptAlias /trac /usr/share/trac/cgi-bin/trac.wsgi And restarted apache # service apache2 restart I could access it using the url: https://test.local/trac I logged in as an admin. I went to https://test.local/trac/admin/versioncontrol/repository Saw no repositories. I added a test one this way: # trac-admin /usr/share/trac/projects/test repository add testrepo /home/svn/repo/testrepo svn My web browser says an empty response was sent. Apache logs show this: (20014)Internal error (specific information not available) Which I found indicates the service it is trying to contact is not responding. But if I manually remove it, then it works: # trac-admin /usr/share/trac/projects/test repository remove testrepo But I have to restart apache first before I can access it again. Then in the trac website, I manually added a repository under svn as the type. And same result. But even if I restart apache, I still can't access it. |
|||
| #13914 | fixed | quick-jump search not working with diff: links | ||
| Description |
If you enter Note: The page displays a notice saying "You arrived here through the quick-jump search feature. To instead search for the term diff:@1:3, click here." If you follow that link then that page shows a quickjump link which works correctly. I've tested this on the 1.4 and 1.6 demo Trac's and they both have this problem. I have previously used this feature with Trac 1.0 when it worked as expected. |
|||
| #13912 | fixed | Message extraction fails with error no such option 'no-default-keywords' | ||
| Description |
extract task failing…. $ make python=310 extract python -Wdefault setup.py extract_messages extract_messages_js extract_messages_tracini running extract_messages ... writing PO template file to trac/locale/messages.pot running extract_messages_js error: error in setup.cfg: command 'extract_messages' has no such option 'no-default-keywords' make: *** [Makefile:208: extract] Error 1 $ ~/venv/py310/bin/python -Wignore setup.py extract_messages >/dev/null $ ~/venv/py310/bin/python -Wignore setup.py extract_messages_js >/dev/null error: error in setup.cfg: command 'extract_messages' has no such option 'no-default-keywords' $ ~/venv/py310/bin/python -Wignore setup.py extract_messages_tracini >/dev/null error: error in setup.cfg: command 'extract_messages' has no such option 'no-default-keywords' Babel 2.18.0 is used. jun66j5@localhost:1426$ ~/venv/py310/bin/pip show Babel Name: babel Version: 2.18.0 Summary: Internationalization utilities Home-page: https://babel.pocoo.org/ Author: Armin Ronacher Author-email: armin.ronacher@active-4.com License: BSD-3-Clause Location: /home/jun66j5/venv/py310/lib/python3.10/site-packages Requires: Required-by: |
|||
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.
The available operators are:
= | the field content exactly matches the 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 |
See also: TracTickets, TracReports, TracGuide
