wiki:TracQuery

Trac Ticket Queries

In addition to reports, Trac provides support for custom ticket queries, which can be used to display tickets that meet specified 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 in and no name/email is 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 on 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.

After you have 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

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 in by placing pipes (|) between the columns:

[[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter)]]

This is displayed as:

Results (1 - 3 of 394)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#515 duplicate python support disabled in qgis - no module named future osgeo4w-dev@… saultdon
#514 fixed python-future seems to be missing as dependency for qgis osgeo4w-dev@… kbevers
#513 fixed JP2MrSID support missing from latest version of gdal-mrsid? osgeo4w-dev@… ogcr
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>:

[[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 394)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#515 duplicate python support disabled in qgis - no module named future osgeo4w-dev@… saultdon
Description

I just upgraded QGIS to 2.16.0 from the OSGeo4W installer and it starts with a python error.

Couldn't load QGIS utils.
Python support will be disabled.


Traceback (most recent call last):
  File "", line 1, in 
  File "C:/GIS/Apps/OSGEO4~1/apps/qgis/./python\qgis\utils.py", line 20, in 
    from future import standard_library
ImportError: No module named future


Python version:
2.7.5 (default, May 15 2013, 22:44:16) [MSC v.1500 64 bit (AMD64)]

QGIS version:
2.16.0-Nødebo 'Nødebo', d0b3e39

Python path:
['C:/GIS/Apps/OSGEO4~1/apps/qgis/./python', u'C:/Users/dcameron/.qgis2/python', u'C:/Users/dcameron/.qgis2/python/plugins', 'C:/GIS/Apps/OSGEO4~1/apps/qgis/./python/plugins', 'C:\\GIS\\Apps\\OSGEO4~1\\apps\\Python27\\lib\\site-packages\\matplotlib-1.3.1-py2.7-win-amd64.egg', 'C:\\GIS\\Apps\\OSGEO4~1\\apps\\Python27\\lib\\site-packages\\nose-1.3.3-py2.7.egg', 'C:\\GIS\\Apps\\OSGEO4~1\\apps\\Python27\\lib\\site-packages\\tornado-4.0.1-py2.7-win-amd64.egg', 'C:\\GIS\\Apps\\OSGEO4~1\\apps\\Python27\\lib\\site-packages\\backports.ssl_match_hostname-3.4.0.2-py2.7.egg', 'C:\\GIS\\Apps\\OSGEO4~1\\apps\\Python27\\lib\\site-packages\\certifi-14.05.14-py2.7.egg', 'C:\\GIS\\Apps\\OSGEO4~1\\apps\\orfeotoolbox\\python', 'C:\\GIS\\Apps\\OSGEO4~1\\bin', 'C:\\GIS\\Apps\\OSGEO4~1\\bin\\python27.zip', 'C:\\GIS\\Apps\\OSGEO4~1\\apps\\Python27\\DLLs', 'C:\\GIS\\Apps\\OSGEO4~1\\apps\\Python27\\lib', 'C:\\GIS\\Apps\\OSGEO4~1\\apps\\Python27\\lib\\plat-win', 'C:\\GIS\\Apps\\OSGEO4~1\\apps\\Python27\\lib\\lib-tk', 'C:\\GIS\\Apps\\OSGEO4~1\\apps\\Python27', 'C:\\GIS\\Apps\\OSGEO4~1\\apps\\Python27\\lib\\site-packages', 'C:\\GIS\\Apps\\OSGEO4~1\\apps\\Python27\\lib\\site-packages\\PIL', 'C:\\GIS\\Apps\\OSGEO4~1\\apps\\Python27\\lib\\site-packages\\jinja2-2.7.2-py2.7.egg', 'C:\\GIS\\Apps\\OSGEO4~1\\apps\\Python27\\lib\\site-packages\\markupsafe-0.23-py2.7-win-amd64.egg', 'C:\\GIS\\Apps\\OSGEO4~1\\apps\\Python27\\lib\\site-packages\\pytz-2012j-py2.7.egg', 'C:\\GIS\\Apps\\OSGEO4~1\\apps\\Python27\\lib\\site-packages\\win32', 'C:\\GIS\\Apps\\OSGEO4~1\\apps\\Python27\\lib\\site-packages\\win32\\lib', 'C:\\GIS\\Apps\\OSGEO4~1\\apps\\Python27\\lib\\site-packages\\Pythonwin', 'C:\\GIS\\Apps\\OSGEO4~1\\apps\\Python27\\lib\\site-packages\\Shapely-1.2.18-py2.7-win-amd64.egg', 'C:\\GIS\\Apps\\OSGEO4~1\\apps\\Python27\\lib\\site-packages\\wx-2.8-msw-unicode']

I think python-future in the installer just needs to be added as a dependency.

#514 fixed python-future seems to be missing as dependency for qgis osgeo4w-dev@… kbevers
Description

It would seem as if python-future is not a dependency for QGIS. This is a problem when upgrading to the new 2.16 release, as the python code imports stuff from the python-future package. QGIS complains about the missing package and then starts without python.

The qgis-dev packages has python-future listed as a dependency, so the problem is most likely to show up for users that don't use the dev-versions.

#513 fixed JP2MrSID support missing from latest version of gdal-mrsid? osgeo4w-dev@… ogcr
Description

Using the OSGeo4W 32bit installer, I've installed the latest "cur" version of gdal, gdal-mrsid, and dependencies that the installer will allow me to (excepting gdal-dev). gdalinfo --formats reveals that mrsid support is loaded and working, however jp2mrsid support is missing. Partial output below:

C:\OSGeo4W3\bin>gdalinfo.exe --version
GDAL 2.1.0, released 2016/04/25

C:\OSGeo4W3\bin>gdalinfo.exe --formats
Supported Formats:
  MG4Lidar -raster- (ro): MrSID Generation 4 / Lidar (.sid)
  MrSID -raster- (rov): Multi-resolution Seamless Image Database (MrSID)
  VRT -raster- (rw+v): Virtual Raster
  GTiff -raster- (rw+vs): GeoTIFF
  NITF -raster- (rw+vs): National Imagery Transmission Format
 --snip--

If I install a previous version (1.9.2) of gdal, gdal-mrsid, and dependencies, mrsid and jp2mrsid formats appear as desired in gdalinfo:

C:\OSGeo4W2\bin>gdalinfo.exe --version
GDAL 1.9.2, released 2012/10/08

C:\OSGeo4W2\bin>gdalinfo.exe --formats
Supported Formats:
  MG4Lidar (ro): MrSID Generation 4 / Lidar (.sid)
  MrSID (rov): Multi-resolution Seamless Image Database (MrSID)
  JP2MrSID (rov): MrSID JPEG2000
  VRT (rw+v): Virtual Raster
  GTiff (rw+v): GeoTIFF
  NITF (rw+v): National Imagery Transmission Format
 --snip--

I also tried the "exp" and the "dev" versions of the "exp" packages, and ended up with the same result of missing JP2MrSID support, but I've omitted the output for the sake of brevity.

Is there a particular reason that JP2MrSID is missing, or am I simply overlooking something obvious? I'm guessing the latter, but I've searched everywhere to see why the support would be removed, or how to enable it some other way, and have come up empty-handed.

GDAL_SKIP of other JP2 drivers seems to have no effect (other than disabling other JP2 drivers) in any case.

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. Filters are separated by ampersands (&). Each filter 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 omitted 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, TicketQuery

Last modified 17 months ago Last modified on Apr 22, 2015 3:35:16 PM