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:

Problem with method "setDescription" in class "ComposedDescription"

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

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#978 fixed Failed to install otrobopt 0.4 with OT 1.11 mrbugs michael.baudin@…
#976 invalid AttributeError: 'module' object has no attribute 'SobolIndicesExperiment' mrbugs rajeevdas25@…
#975 fixed EmpiricalBernsteinCopula is a copula as sample is truncated mrbugs haddad
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 911)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#978 fixed Failed to install otrobopt 0.4 with OT 1.11 mrbugs michael.baudin@…

I tried to install otrobopt with anaconda on Windows, but failed to load the version 0.4 of the package :

(base) C:\Users\MYACCOUNT>conda install otrobopt Solving environment: done ## Package Plan ##

environment location: C:\Users\MYACCOUNT\AppData\Local\Continuum\anaconda3 added / updated specs:

  • otrobopt

The following NEW packages will be INSTALLED:

otrobopt: 0.4-py36_1000 conda-forge

Proceed ([y]/n)? Preparing transaction: done Verifying transaction: done Executing transaction: done

(base) C:\Users\MYACCOUNT>python Python 3.6.5 |Anaconda, Inc.| (default, Mar 29 2018, 13:32:41) [MSC v.1900 64 bit (AMD64)] on win32 Type "help", "copyright", "credits" or "license" for more information.

import otrobopt

Traceback (most recent call last):

File "C:\Users\MYACCOUNT\AppData\Local\Continuum\anaconda3\lib\site-packages\otrobopt\", line 17, in swig_import_helper

return importlib.import_module(mname)

File "C:\Users\MYACCOUNT\AppData\Local\Continuum\anaconda3\lib\importlib\", line 126, in import_module

return _bootstrap._gcd_import(name[level:], package, level)

File "<frozen importlib._bootstrap>", line 994, in _gcd_import File "<frozen importlib._bootstrap>", line 971, in _find_and_load File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 658, in _load_unlocked File "<frozen importlib._bootstrap>", line 571, in module_from_spec File "<frozen importlib._bootstrap_external>", line 922, in create_module File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed

ImportError: DLL load failed: La procédure spécifiée est introuvable.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):

File "<stdin>", line 1, in <module> File "C:\Users\MYACCOUNT\AppData\Local\Continuum\anaconda3\lib\site-packages\otrobopt\", line 16, in <module>

from .otrobopt import *

File "C:\Users\MYACCOUNT\AppData\Local\Continuum\anaconda3\lib\site-packages\otrobopt\", line 20, in <module>

_otrobopt = swig_import_helper()

File "C:\Users\MYACCOUNT\AppData\Local\Continuum\anaconda3\lib\site-packages\otrobopt\", line 19, in swig_import_helper

return importlib.import_module('_otrobopt')

File "C:\Users\MYACCOUNT\AppData\Local\Continuum\anaconda3\lib\importlib\", line 126, in import_module

return _bootstrap._gcd_import(name[level:], package, level)

ModuleNotFoundError: No module named '_otrobopt'

I tried to install the v0.3, with the same result.

#976 invalid AttributeError: 'module' object has no attribute 'SobolIndicesExperiment' mrbugs rajeevdas25@…


I have installed OpenTurns on a Windows machine (Win7). While running a piece of code I am getting an error message as 'AttributeError: 'module' object has no attribute 'SobolIndicesExperiment

I used the package 'OpenTURNS1.12rc1 ' from the path provided below Download the installer matching your python version and architecture from GitHub

I used the following lines, which throws the error from ot.SobolIndicesExperiment

import pandas as pd import openturns as ot import xlrd import numpy as np import matplotlib.pyplot as plt from matplotlib import interactive import shutil import os

N = 4 distribution = ot.ComposedDistribution([ot.Uniform(25000.06, 35000.09), ot.Uniform(35, 50), ot.Uniform(5, 20), ot.Uniform(0.95 , 1.05), ot.Uniform(0.3135, 0.3465), ot.Uniform(21.375, 23.625)]) design = ot.SobolIndicesExperiment(distribution, N, True).generate() dataMatrix = np.array(design)

Just to cross verify , I tried the following lines too with sobol, and for the sequence they work, but not SobolIndicesExperiment

sequence = ot.SobolSequence(6) experiment = sequence.generate(5) sample = np.array(experiment)

Am I missing any dependencies? and is there a way to avoid this issue? Any help would be greatly appreciated.

Thank you,


#975 fixed EmpiricalBernsteinCopula is a copula as sample is truncated mrbugs haddad

Hi, When defining an EmpiricalBernsteinCopula, the result should be a Copula if sample is truncated such as its size becomes a multiple of binNumber

Here an example that illustrate the issue :

import openturns as ot
x = ot.Normal(3).getSample(1000)
copula = ot.BernsteinCopulaFactory().build(x)
estimated_dist = ot.ComposedDistribution([ot.Normal()]*3, copula)

which returns :

TypeError: InvalidArgumentException : Error: the given distribution=class=EmpiricalBernsteinCopula name=EmpiricalBernsteinCopula dimension=3 copulaSample=class=Sample name=Unnamed implementation=class=SampleImplementation name=Unnamed size=990 dimension=3 description=[X0,X1,X2] data=[[0.733333,0.10404,0.315152],[0.89697,0.0151515,0.614141],[0.357576,0.927273,0.788889],...,[0.892929,0.411111,0.209091],[0.476768,0.913131,0.374747],[0.227273,0.142424,0.275758]] binNumber=11 is not a copula.

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 6 years ago Last modified on 04/08/13 16:20:19