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

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.

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

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:

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.

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:

0

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

Ticket	Resolution	Summary	Owner	Reporter
#366	fixed	obspy modules install issues		c.miller@…
#364	fixed	seishub.client.station.getPAZ() can not handle referenced responses	megies	megies
#363	fixed	Problem with reading sac data	barsch	estelle.cros@…

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

Ticket	Resolution	Summary	Owner	Reporter
#366	fixed	obspy modules install issues		c.miller@…
Reported by c.miller@…, 5 days ago.
Description	Hi I'm having issues installing certain obspy modules, namely obspy.mseed, obspy.gse2, obspy.signal, obspy.taup. Obspy.core and the other modules all install ok. I get the following error from the obspy.mseed module. [root@tanna ~]# easy_install obspy.mseed Searching for obspy.mseed Reading  http://pypi.python.org/simple/obspy.mseed/ Reading  http://www.obspy.org Best match: obspy.mseed 0.6.1 Downloading  http://pypi.python.org/packages/source/o/obspy.mseed/obspy.mseed-0.6.1.zip#md5=f822b8d4de5d5422d31cee443e64eb92 Processing obspy.mseed-0.6.1.zip Writing /tmp/easy_install-c8wXTQ/obspy.mseed-0.6.1/setup.cfg Running obspy.mseed-0.6.1/setup.py -q bdist_egg --dist-dir /tmp/easy_install-c8wXTQ/obspy.mseed-0.6.1/egg-dist-tmp-E96hxJ unable to execute gcc: No such file or directory error: Setup script exited with error: command 'gcc' failed with exit status 1 I'm running on CentOs6.2 64bit I've installed python using the epd free package and it seems to have installed ok. Any help appreciated. Thanks Craig Miller GNS Science
#364	fixed	seishub.client.station.getPAZ() can not handle referenced responses	megies	megies
Reported by megies, 9 days ago.
Description	getPAZ() is not able to follow PAZ information not included directly in the station_control_header as response_poles_and_zeros (blk 53) and channel_sensitivity_gain (blk 58) but rather referenced via a response_reference (blk 60) with the actual information included in the abbreviation_dictionary_control_header (see attached example). How about using the xseed Parser internally in the seishub client to do the parsing and use the Parsers getPAZ() method, removing this duplicated (and less flexible) code piece? Any obvious problems with that?
#363	fixed	Problem with reading sac data	barsch	estelle.cros@…
Reported by estelle.cros@…, 3 weeks ago.
Description	Dear all, I am trying to read sac data and I encounter some problems. I tried the file proposed in example in the website ( http://examples.obspy.org/RJOB_061005_072159.ehz.new) and obspy works fine. But when I used my data it is not working. I think that comes from how the data were constructed but I was wondering if there is a way to do something to make my file readable. The errors obtained when I am trying to read my files are: " >>> from obspy.core import read >>> st = read('obs03.pseg.sac') >>> print st Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib/python2.7/site-packages/obspy.core-0.6.2-py2.7.egg/obspy/core/stream.py", line 533, in __str__ out = out + "\n".join([tr.__str__(id_length) for tr in self]) File "/usr/lib/python2.7/site-packages/obspy.core-0.6.2-py2.7.egg/obspy/core/trace.py", line 373, in __str__ return out % (self.stats) ValueError: unsupported format character '.' (0x2e) at index 10 Under gsac, the header associated to this file is: NPTS 450000 B 0 E 3599.992 DELTA 0.008 DEPMAX 98459 DEPMIN -106333 DEPMEN -0.5771466 NZYEAR 2011 NZJDAY 107 NZHOUR 17 NZMIN 0 NZSEC 0 NZMSEC 0 KZDATE Apr 17 (107), 2011 KZTIME 17:00:00.000 KSTNM KCMPNM SHN STLA 0 STLO 0 TIMMAX 2871.872 TIMMIN 2871.776 NVHDR 6 IFTYPE ITIME IDEP IVOLTS IZTYPE IUNKN LPSPOL FALSE LOVROK FALSE LCALDA FALSE Thank you. Best regards EC

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