Edgewall Software

This page documents the 0.11 release. Documentation for other releases can be found here.

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.

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.

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.

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.

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:

#181, #204, #226, #239, #351, #413, #450, #475, #519, #529

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:

10

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:

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

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#13423 invalid print "usage: "+sys.argv[0]+" socket trac_dir" anonymous
Description

Regarding ticket https://trac.edgewall.org/ticket/13422 I instaled

 pip install https://download.edgewall.org/trac/Trac-1.5.3-py3-none-any.whl

But can't run this by screen

screen trac-fcgi /usr/home/userman/domains/soemdomain.com/fastcgi0.sock /usr/home/userman/tracx/mydir
File "/usr/local/company/bin/trac-fcgi", line 10
print "usage: "+sys.argv[0]+" socket trac_dir"
^
SyntaxError: Missing parentheses in call to 'print'. Did you mean print("usage: "+sys.argv[0]+" socket trac_dir")? 

By this command working track Trac-1.4.3-py2-none-any.whl on python27 But not wokring Trac-1.5.3-py3-none-any.whl on python 3.8

#13422 invalid except TypeError, e: anonymous
Description
trac-admin domains/domainmy.com/public/ initenv
Traceback (most recent call last):
  File "/usr/home/userhere/.virtualenvs/venvpython37/bin/trac-admin", line 5, in <module>
    from trac.admin.console import run
  File "/usr/home/userhere/.virtualenvs/venvpython37/lib/python3.7/site-packages/trac/admin/__init__.py", line 14, in <module>
    from trac.admin.api import *
  File "/usr/home/userhere/.virtualenvs/venvpython37/lib/python3.7/site-packages/trac/admin/api.py", line 14, in <module>
    from trac.core import *
  File "/usr/home/userhere/.virtualenvs/venvpython37/lib/python3.7/site-packages/trac/core.py", line 205
    except TypeError, e:
                    ^
SyntaxError: invalid syntax
  Downloading Trac-1.4.3.tar.gz (5.7 MB)
     |████████████████████████████████| 5.7 MB 3.3 MB/s 
    ERROR: Command errored out with exit status 1:
     command: /usr/home/userhere/venvpython37/bin/python3.7 -c 'import io, os, sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-kuertgql/trac_4bfc3f81da9e4efeb698ea62fb20e1f6/setup.py'"'"'; __file__='"'"'/tmp/pip-install-kuertgql/trac_4bfc3f81da9e4efeb698ea62fb20e1f6/setup.py'"'"';f = getattr(tokenize, '"'"'open'"'"', open)(__file__) if os.path.exists(__file__) else io.StringIO('"'"'from setuptools import setup; setup()'"'"');code = f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info --egg-base /tmp/pip-pip-egg-info-6hiw8oji
         cwd: /tmp/pip-install-kuertgql/trac_4bfc3f81da9e4efeb698ea62fb20e1f6/
    Complete output (1 lines):
    Trac doesn't support Python 3 (yet)
    ----------------------------------------
WARNING: Discarding https://files.pythonhosted.org/packages/cc/aa/9e3415901caa2d12a7cc25fea70f160bdb62a59cbc39a05e4befca832e5f/Trac-1.4.3.tar.gz#sha256=c93ceed9abee6e3c7789f469862e82a3b9bf3405be73aae3221b5c259e062d21 (from https://pypi.org/simple/trac/). Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.
  Downloading Trac-1.4.2.tar.gz (5.6 MB)
     |████████████████████████████████| 5.6 MB 5.6 MB/s 


#13421 duplicate ImportError: cannot import name 'soft_unicode' from 'jinja2.utils' Tomasz Brzezina <tomasz@…>
Description

I installed https://download.edgewall.org/trac/Trac-1.5.3.tar.gz (BTW there's no Trac-latest.zip which is mentioned here 1.5/TracInstall)

After installation trac-admin result is:

Traceback (most recent call last):
  File "/usr/local/bin/trac-admin", line 5, in <module>
    from trac.admin.console import run
  File "/usr/local/lib/python3.9/dist-packages/trac/admin/console.py", line 34, in <module>
    from trac.env import Environment
  File "/usr/local/lib/python3.9/dist-packages/trac/env.py", line 52, in <module>
    from trac.web.chrome import Chrome
  File "/usr/local/lib/python3.9/dist-packages/trac/web/chrome.py", line 40, in <module>
    from trac.mimeview.api import RenderingContext, get_mimetype
  File "/usr/local/lib/python3.9/dist-packages/trac/mimeview/__init__.py", line 14, in <module>
    from trac.mimeview.api import *
  File "/usr/local/lib/python3.9/dist-packages/trac/mimeview/api.py", line 70, in <module>
    from trac.resource import Resource
  File "/usr/local/lib/python3.9/dist-packages/trac/resource.py", line 21, in <module>
    from trac.util.presentation import classes
  File "/usr/local/lib/python3.9/dist-packages/trac/util/presentation.py", line 26, in <module>
    from jinja2.utils import soft_unicode
ImportError: cannot import name 'soft_unicode' from 'jinja2.utils' (/usr/local/lib/python3.9/dist-packages/jinja2/utils.py)



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.

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

Last modified 11 years ago Last modified on Apr 10, 2010, 6:37:10 PM
Note: See TracWiki for help on using the wiki.