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.

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

Ticket Resolution Summary Owner Reporter
#1566 fixed r.colors Makefile: help page missing rules with underscores in the name grass-dev@… hamish
#1562 fixed Introduction of spatial and temporal vertical units for raster3d maps and r3.support huhabla huhabla
#1560 invalid v.db.connect failed grass-dev@… lucadelu

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

Ticket Resolution Summary Owner Reporter
#1566 fixed r.colors Makefile: help page missing rules with underscores in the name grass-dev@… hamish

Reported by hamish, 4 days ago.
description

Hi,

the grass7 help page for r.colors is missing the preview images for population_dens and precipitation_monthly, perhaps because the following sed substitution is failing in the Makefile doesn't like the underscores in their names: 

sed 's!^<DD><b>\([a-z0-9.]*\)</b>:!<DD><img width="80" height="12" src="Colortable_\1.png"> <b>\1</b>:!' "$@" > "$@.tmp"

?

the images are generated and copied into $GISBASE/docs/html/ correctly, just missing their reference in the .html file.

thanks, Hamish

#1562 fixed Introduction of spatial and temporal vertical units for raster3d maps and r3.support huhabla huhabla

Reported by huhabla, 10 days ago.
description

I need to add vertical units support to raster3d maps to distinguish between voxel cubes with 3 spatial dimensions or space-time voxel cubes with two spatial and one temporal dimension. These units may be spatial or temporal, based on unit definitions introduced in gis.h, datetime.h and lib/gis/units.c. This results in several modifications in lib/gis and lib/raster3d and lib/python. The current raster3d header format will change, but backward compatibility is assured. I have attached a patch including the new module "r3.support".

The temporal units and the top-bottom resolution can/will be used as relative time using the datetime library and the temporal GIS library to allow spatio-temporal space-time cube processing.

The module r3.support allows the creation/modification of title, description, history and spatio-temporal units for raster3d maps.

#1560 invalid v.db.connect failed grass-dev@… lucadelu

Reported by lucadelu, 10 days ago.
description

Using v.db.join I obtain this error related to v.db.connect 

+ v.db.connect -gl map=comuni fs=| layer=1
+ cut -d| -f4
*** glibc detected *** v.db.connect: free(): invalid pointer: 0x00007fdd364c33d8 ***
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x78a8f)[0x7fdd33ba2a8f]
/lib/x86_64-linux-gnu/libc.so.6(cfree+0x73)[0x7fdd33ba68e3]
/home/luca/compilati/grass6_devel/dist.x86_64-unknown-linux-gnu/lib/libgrass_vect.6.5.svn.so(Vect_set_organization+0x20)[0x7fdd360ba960]
/home/luca/compilati/grass6_devel/dist.x86_64-unknown-linux-gnu/lib/libgrass_vect.6.5.svn.so(Vect__init_head+0x30)[0x7fdd360bb830]
/home/luca/compilati/grass6_devel/dist.x86_64-unknown-linux-gnu/lib/libgrass_vect.6.5.svn.so(Vect__open_old+0x85)[0x7fdd360c5705]
v.db.connect(main+0x3af)[0x401ccf]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xff)[0x7fdd33b48eff]
v.db.connect[0x401859]
======= Memory map: ========
00400000-00403000 r-xp 00000000 09:02 29626241                           /home/luca/compilati/grass6_devel/dist.x86_64-unknown-linux-gnu/bin/v.db.connect
00603000-00604000 r--p 00003000 09:02 29626241                           /home/luca/compilati/grass6_devel/dist.x86_64-unknown-linux-gnu/bin/v.db.connect
00604000-00605000 rw-p 00004000 09:02 29626241                           /home/luca/compilati/grass6_devel/dist.x86_64-unknown-linux-gnu/bin/v.db.connect
0136b000-0138c000 rw-p 00000000 00:00 0                                  [heap]
7fdd24000000-7fdd24021000 rw-p 00000000 00:00 0 
7fdd24021000-7fdd28000000 ---p 00000000 00:00 0 
7fdd2bedf000-7fdd2c186000 r--p 00000000 09:00 131627                     /usr/lib/locale/locale-archive
7fdd2c186000-7fdd2c189000 r-xp 00000000 09:00 805048                     /lib/x86_64-linux-gnu/libgpg-error.so.0.8.0
7fdd2c189000-7fdd2c388000 ---p 00003000 09:00 805048                     /lib/x86_64-linux-gnu/libgpg-error.so.0.8.0
7fdd2c388000-7fdd2c389000 r--p 00002000 09:00 805048                     /lib/x86_64-linux-gnu/libgpg-error.so.0.8.0
7fdd2c389000-7fdd2c38a000 rw-p 00003000 09:00 805048                     /lib/x86_64-linux-gnu/libgpg-error.so.0.8.0
7fdd2c38a000-7fdd2c399000 r-xp 00000000 09:00 815083                     /usr/lib/x86_64-linux-gnu/libtasn1.so.3.1.9
7fdd2c399000-7fdd2c599000 ---p 0000f000 09:00 815083                     /usr/lib/x86_64-linux-gnu/libtasn1.so.3.1.9
7fdd2c599000-7fdd2c59a000 r--p 0000f000 09:00 815083                     /usr/lib/x86_64-linux-gnu/libtasn1.so.3.1.9
7fdd2c59a000-7fdd2c59b000 rw-p 00010000 09:00 815083                     /usr/lib/x86_64-linux-gnu/libtasn1.so.3.1.9
7fdd2c59b000-7fdd2c611000 r-xp 00000000 09:00 805050                     /lib/x86_64-linux-gnu/libgcrypt.so.11.6.0
7fdd2c611000-7fdd2c811000 ---p 00076000 09:00 805050                     /lib/x86_64-linux-gnu/libgcrypt.so.11.6.0
7fdd2c811000-7fdd2c812000 r--p 00076000 09:00 805050                     /lib/x86_64-linux-gnu/libgcrypt.so.11.6.0
7fdd2c812000-7fdd2c815000 rw-p 00077000 09:00 805050                     /lib/x86_64-linux-gnu/libgcrypt.so.11.6.0
7fdd2c815000-7fdd2c8af000 r-xp 00000000 09:00 815089                     /usr/lib/x86_64-linux-gnu/libgnutls.so.26.14.12
7fdd2c8af000-7fdd2caaf000 ---p 0009a000 09:00 815089                     /usr/lib/x86_64-linux-gnu/libgnutls.so.26.14.12
7fdd2caaf000-7fdd2cab5000 r--p 0009a000 09:00 815089                     /usr/lib/x86_64-linux-gnu/libgnutls.so.26.14.12
7fdd2cab5000-7fdd2cab6000 rw-p 000a0000 09:00 815089                     /usr/lib/x86_64-linux-gnu/libgnutls.so.26.14.12
7fdd2cab6000-7fdd2cacf000 r-xp 00000000 09:00 133738                     /usr/lib/libsasl2.so.2.0.23
7fdd2cacf000-7fdd2ccce000 ---p 00019000 09:00 133738                     /usr/lib/libsasl2.so.2.0.23
7fdd2ccce000-7fdd2cccf000 r--p 00018000 09:00 133738                     /usr/lib/libsasl2.so.2.0.23
7fdd2cccf000-7fdd2ccd0000 rw-p 00019000 09:00 133738                     /usr/lib/libsasl2.so.2.0.23
7fdd2ccd0000-7fdd2cce7000 r-xp 00000000 09:00 787026                     /lib/x86_64-linux-gnu/libresolv-2.13.so
7fdd2cce7000-7fdd2cee7000 ---p 00017000 09:00 787026                     /lib/x86_64-linux-gnu/libresolv-2.13.so
7fdd2cee7000-7fdd2cee8000 r--p 00017000 09:00 787026                     /lib/x86_64-linux-gnu/libresolv-2.13.so
7fdd2cee8000-7fdd2cee9000 rw-p 00018000 09:00 787026                     /lib/x86_64-linux-gnu/libresolv-2.13.so
7fdd2cee9000-7fdd2ceeb000 rw-p 00000000 00:00 0 
7fdd2ceeb000-7fdd2ceed000 r-xp 00000000 09:00 815099                     /lib/x86_64-linux-gnu/libkeyutils.so.1.3
7fdd2ceed000-7fdd2d0ec000 ---p 00002000 09:00 815099                     /lib/x86_64-linux-gnu/libkeyutils.so.1.3
7fdd2d0ec000-7fdd2d0ed000 r--p 00001000 09:00 815099                     /lib/x86_64-linux-gnu/libkeyutils.so.1.3
7fdd2d0ed000-7fdd2d0ee000 rw-p 00002000 09:00 815099                     /lib/x86_64-linux-gnu/libkeyutils.so.1.3
7fdd2d0ee000-7fdd2d0f5000 r-xp 00000000 09:00 815155                     /usr/lib/x86_64-linux-gnu/libkrb5support.so.0.1
7fdd2d0f5000-7fdd2d2f4000 ---p 00007000 09:00 815155                     /usr/lib/x86_64-linux-gnu/libkrb5support.so.0.1
7fdd2d2f4000-7fdd2d2f5000 r--p 00006000 09:00 815155                     /usr/lib/x86_64-linux-gnu/libkrb5support.so.0.1
7fdd2d2f5000-7fdd2d2f6000 rw-p 00007000 09:00 815155                     /usr/lib/x86_64-linux-gnu/libkrb5support.so.0.1
7fdd2d2f6000-7fdd2d31b000 r-xp 00000000 09:00 815129                     /usr/lib/x86_64-linux-gnu/libk5crypto.so.3.1
7fdd2d31b000-7fdd2d51b000 ---p 00025000 09:00 815129                     /usr/lib/x86_64-linux-gnu/libk5crypto.so.3.1
7fdd2d51b000-7fdd2d51c000 r--p 00025000 09:00 815129                     /usr/lib/x86_64-linux-gnu/libk5crypto.so.3.1
7fdd2d51c000-7fdd2d51d000 rw-p 00026000 09:00 815129                     /usr/lib/x86_64-linux-gnu/libk5crypto.so.3.1
7fdd2d51d000-7fdd2e35d000 r--p 00000000 09:00 131694                     /usr/lib/libicudata.so.44.2
7fdd2e35d000-7fdd2e55c000 ---p 00e40000 09:00 131694                     /usr/lib/libicudata.so.44.2
7fdd2e55c000-7fdd2e55d000 rw-p 00e3f000 09:00 131694                     /usr/lib/libicudata.so.44.2
7fdd2e55d000-7fdd2e56a000 r-xp 00000000 09:00 134705                     /usr/lib/liblber-2.4.so.2.5.6
7fdd2e56a000-7fdd2e769000 ---p 0000d000 09:00 134705                     /usr/lib/liblber-2.4.so.2.5.6
7fdd2e769000-7fdd2e76a000 r--p 0000c000 09:00 134705                     /usr/lib/liblber-2.4.so.2.5.6
7fdd2e76a000-7fdd2e76b000 rw-p 0000d000 09:00 134705                     /usr/lib/liblber-2.4.so.2.5.6
7fdd2e76b000-7fdd2e79c000 r-xp 00000000 09:00 148895                     /usr/lib/libidn.so.11.6.1
7fdd2e79c000-7fdd2e99c000 ---p 00031000 09:00 148895                     /usr/lib/libidn.so.11.6.1
7fdd2e99c000-7fdd2e99d000 r--p 00031000 09:00 148895                     /usr/lib/libidn.so.11.6.1Aborted

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