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

Ticket Resolution Summary Owner Reporter
#448 fixed OGR2OGR Cannot Open Shapefile in to SQL Server 2014 osgeo4w-dev@… nrakich
#447 fixed gdal is missing libpng dependency osgeo4w-dev@… mwtoews
#445 worksforme QGIS 2.6 doesn't install (crssync and qgis-bin missing msvc210.dll) osgeo4w-dev@… saultdon

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

Ticket Resolution Summary Owner Reporter
#448 fixed OGR2OGR Cannot Open Shapefile in to SQL Server 2014 osgeo4w-dev@… nrakich

Reported by nrakich, 2 weeks ago.

description

Hello,

Ogr2ogr does not seem able to open shapefiles with SQL Server 2014 drivers (for loading, reprojecting to the database). Are there any patches that can be applied that would resolve this? I am able to successfully load them to SQL Server 2012.

Syntax [removed server and database name] ogr2ogr -f "MSSQLSpatial" "MSSQL:server=[SERVERNAME];database=[DBNAME];trusted_connection=yes" "cb_2013_55_tract_500k.shp" -s_srs "EPSG:4269" -t_srs "EPSG:4326" -overwrite -lco "GEOM_TYPE=geography" -lco "GEOM_NAME=geog4326" -nln "ShapeWiCensusTract?"

Reply "Unable to open datasource 'cb_2015_55_tract.shp' with the following drivers". (then list of about 45 drivers, including MSSQLSpatial, which is specified in the command line.

Best Regards, Nick

#447 fixed gdal is missing libpng dependency osgeo4w-dev@… mwtoews

Reported by mwtoews, 4 weeks ago.

description

With a fresh install of OSGeo4W64, installing gdal and attempting gdalinfo shows an error message:

gdalinfo.exe - System Error: The program can't start because libpng16.dll is missing from your computer...

Re-running setup and adding libpng fixed it.

#445 worksforme QGIS 2.6 doesn't install (crssync and qgis-bin missing msvc210.dll) osgeo4w-dev@… saultdon

Reported by saultdon, 7 weeks ago.

description

During installation on Windows 8.1 (64bit), when the qgis-common.bat is run during postinstall crssync.exe crashes because of a missing dll and then afterwards, qgis-bin.exe complains about the missing dll as well.

I was able to get it installed without error when manually installing msvcrt2013. Does it need to be added as a dependency for QGIS 2.6?

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