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:

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 using 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 306)

Ticket Resolution Summary Owner Reporter
#427 duplicate OSGeo4W-64bit: qgis - crssync problems osgeo4w-dev@… hellik
#426 duplicate g.proj: projection can't be determined (64bit) osgeo4w-dev@… hellik
#425 fixed lack of zip_decoder in PIL with Windows 64bits installer osgeo4w-dev@… nonolingenieur

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

Ticket Resolution Summary Owner Reporter
#427 duplicate OSGeo4W-64bit: qgis - crssync problems osgeo4w-dev@… hellik

Reported by hellik, 3 weeks ago.

description

from the ML:

 http://lists.osgeo.org/pipermail/osgeo4w-dev/2014-July/002763.html

Package: qgis-common
    qgis-common.bat exit code -1073741515
Package: qgis-dev
	qgis-dev.bat exit code -1073741515

from the log file, it seems to be a crssync issue?

C:\OSGeo4W64>"C:\OSGEO4~1\apps\qgis-dev\crssync"

2014/07/07 09:16:22 abnormal exit: exit code=-1073741515
2014/07/07 09:30:56 note: Installation abgeschlossen
2014/07/07 09:30:56 Ending OSGeo4W install
#426 duplicate g.proj: projection can't be determined (64bit) osgeo4w-dev@… hellik

Reported by hellik, 3 weeks ago.

description

from the ML:

 http://lists.osgeo.org/pipermail/osgeo4w-dev/2014-July/002764.html

>> warning: projection can't be determined
>> modul can't be executed
>> command C:/OSGEO~1/apps/qgis/./grass/modules/qgis.g.info info=proj
>> <br><br> 
>> any idea?
>
>Not really.  I can open the gtopo30 map from the qgis_sample_data set just
>fine.

ok, it seems the underlying problem is in a broken OSGeo4W-GRASS6.4.3-5
64bit. 

I can start a GRASS session only in text mode because g.proj (and some other
modules, e.g. g.region, g.setproj) seems to be broken in
OSGeo4W-GRASS6.4.3-5 64 bit.

in a GRASS session in text mode I can start the module GUI e.g. by

GRASS 6.4.3 (nc_spm_08)> g.mlist --ui

or get the manual by

GRASS 6.4.3 (nc_spm_08)> g.mlist --help

Beschreibung:
 Liste vorhandene GRASS Datenbank-Dateien eines vom Nutzer bestimmten
Datentyps
und verwende optional ein Suchmuster.

Schlüsselwörter:
 Allgemein, Kartenverwaltung

but I can not do this for g.proj, g.region, g.setproj; therefore the QGIS
error:

>> command C:/OSGEO~1/apps/qgis/./grass/modules/qgis.g.info info=proj
>> <br><br>

as the underlying GRASS module isn't working correctly.

tested on 2 different win boxes.

#425 fixed lack of zip_decoder in PIL with Windows 64bits installer osgeo4w-dev@… nonolingenieur

Reported by nonolingenieur, 4 weeks ago.

description

I've meet problems to decode PNG files with PIL from a QGIS plugin with Windows 64 bits version of QGIS standalone installer, based on OSGeo4W.

I don't have zip_decoder in binary _image.pyd

A workaround is to overwrite PIL in QGIS folder with files from PIL standalone installer.

I've printed methods PIL.Image.core.*_decoder

from QGIS 2.4 64bits:

bit_decoder fli_decoder gif_decoder hex_decoder msp_decoder packbits_decoder pcd_decoder pcx_decoder raw_decoder sun_rle_decoder tga_rle_decoder tiff_lzw_decoder xbm_decoder

from QGIS 2.2 32bits:

bit_decoder fli_decoder gif_decoder hex_decoder jpeg_decoder msp_decoder packbits_decoder pcd_decoder pcx_decoder raw_decoder sun_rle_decoder tga_rle_decoder tiff_lzw_decoder xbm_decoder zip_decoder

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