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

Ticket Resolution Summary Owner Reporter
#90 duplicate type inference failure in ghc/hugs extensions nobody guest
#87 invalid Strange writeFile behaviour nobody guest
#85 fixed Force Cabal use in-place Hugs when buiding from source nobody guest

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

Ticket Resolution Summary Owner Reporter
#90 duplicate type inference failure in ghc/hugs extensions nobody guest

Reported by guest, 4 years ago.
description

Oleg recently posted on the mailing list haskell@… a magic coercion that makes pairs of numbers (x,y) behave as complex numbers. Aside from context, the type should be (a,a). The trick works with option -fglasgow-exts in ghc releases at least since 6.8.3. However in hugs Sept 2006 under option -98, it fails type inference. As I understand the documentation, option -98 is supposed to support the necessary extensions in common with ghc.

Is the inconsistent handling of the attached fragment a bug, a feature, or perhaps an undefined corner of the semantics?

Doug McIlroy? doug@…

#87 invalid Strange writeFile behaviour nobody guest

Reported by guest, 5 years ago.
description

I don't understand the following behaviour of writeFile in Hugs. GHCi does what I would expect. Any help would be greatly appreciated!

Matthew Naylor (mfn@cs.york.ac.uk) 

mfn@pc093:/tmp$ ghci
GHCi, version 6.8.2: http://www.haskell.org/ghc/  :? for help
Loading package base ... linking ... done.
Prelude> writeFile "foo.txt" [toEnum 128]
Prelude> Leaving GHCi.
mfn@pc093:/tmp$ wc -c foo.txt 
1 foo.txt
mfn@pc093:/tmp$ rm foo.txt
mfn@pc093:/tmp$ hugs
__   __ __  __  ____   ___      _________________________________________
||   || ||  || ||  || ||__      Hugs 98: Based on the Haskell 98 standard
||___|| ||__|| ||__||  __||     Copyright (c) 1994-2005
||---||         ___||           World Wide Web: http://haskell.org/hugs
||   ||                         Report bugs to: hugs-bugs@haskell.org
||   || Version: May 2006       _________________________________________

Haskell 98 mode: Restart with command line option -98 to enable extensions

Type :? for help
Hugs> writeFile "foo.txt" [toEnum 128]
Hugs> [Leaving Hugs]
mfn@pc093:/tmp$ wc -c foo.txt
2 foo.txt
#85 fixed Force Cabal use in-place Hugs when buiding from source nobody guest

Reported by guest, 5 years ago.
description

I have been experimenting with building Hugs from a source tarball on a computer with no Haskell stuff preinstalled at all.

I noticed that the build fails when running Setup configure for any package because Cabal cannot find Hugs executable.

OTOH, if there is Hugs installed earlier (on the PATH), output from Setup configure shows that the previously installed Hugs is used, not one just built.

This can be easily fixed if proper --with-hugs command line argument is provided to Setup. This affects two files: libraries/Makefile.in and libraries/tools/convert_libraries.

Also, if any package installed has configure script invoking runhugs, this would fail too because in-place runhugs is not on the path. This is fixed by exporting proper PATH variable from the convert_libraries script before running Setup configure.

Proposed patch is attached.

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