Trac Ticket Queries
Table of Contents
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.
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
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.
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:
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:
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 228)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #360 | duplicate | Compile QGIS against Spatialite 4.0 | osgeo4w-dev@… | micha |
| #358 | wontfix | Cannot start QGIS from OSGeo4W terminal - qgis_core.dll is missing | osgeo4w-dev@… | saultdon |
| #356 | fixed | Bat file location independence | jef | anguscarr |
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 228)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #360 | duplicate | Compile QGIS against Spatialite 4.0 | osgeo4w-dev@… | micha |
| description |
Spatialite version 4.0 is the current recommended stable version. QGIS master is compiles against the older spatialite 3.0.1. The required data provider libraries have been uploaded to qgis trunk by the spatialite developer: http://hub.qgis.org/projects/quantum-gis/repository/revisions/47097b72b851a6637a6ceca737ae5d9d04b3b9b0 Spatialite 3.0 is 2 years old, and no longer maintained. Version 4.0 has some nice added features. Can future builds (and certainly 2.0 final) be built with support for spatialite 4.0 ?? Thanks, Micha |
|||
| #358 | wontfix | Cannot start QGIS from OSGeo4W terminal - qgis_core.dll is missing | osgeo4w-dev@… | saultdon |
| description |
I can start QGIS 1.8 from the icons either on the desktop or the start menu, but I can't start QGIS from the OSGeo4W terminal. The error that pops up says: "qgis.exe - System Error, The program can't start because qgis_core.dll is missing from your computer. Try reinstalling the program to fix this problem." I tried a re-install but still get this error when launching qgis from the terminal. I usually always have this terminal open to quickly launch applications and scripts =) |
|||
| #356 | fixed | Bat file location independence | jef | anguscarr |
| description |
The BAT files in OSGEO4w\bin are not all location independant. I want to set the program up to be location independant, so that I can make a portable version. List of files I need to change to make this work: qgis-dev.bat qgis.bat qgis-browser.bat grass64.bat qgis-dev-browser.bat They all initially start with set OSGEO4W_ROOT=<<My install location>> call %OSGEO4W_ROOT%\o4w_env.bat I changed them to start with call %~dp0\o4w_env.bat The bat files are now portable (afaik). Can we change the template files to reflect this change? Then I can package up an installer for distribution based on my local install. I'm sure there are issues with that, like the MSVC runtime installer, but I will work towards fixing those in the installer. |
|||
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
