Version 3 (modified by trac, 8 years ago) (diff)


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.


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.



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:


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:


This is displayed as:

Full rows

In table format you can also have full rows by using rows=<field> like below:


This is displayed as:

Results (1 - 3 of 10752)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#14814 duplicate -g causes "cc failed in phase Assembler" in yaml package Fuuzetsu
git clone
cd yaml
git checkout yaml-0.8.28
stack build yaml --resolver=lts-10.5 --ghc-options='-g'

With this I get (I'm using nix below but should be irrelevant):

[nix-shell:~/programming/yaml]$ stack build yaml --nix -j1 --resolver=lts-10.5 --ghc-options='-g'
raw-strings-qq-1.1: download
raw-strings-qq-1.1: configure
raw-strings-qq-1.1: build
raw-strings-qq-1.1: copy/register
Building all executables for `yaml' once. After a successful build of all of them, only specified executables will be rebuilt.
yaml-0.8.28: configure (lib + exe)
Configuring yaml-0.8.28...
yaml-0.8.28: build (lib + exe)
Preprocessing library for yaml-0.8.28..
Building library for yaml-0.8.28..
[ 1 of 10] Compiling Text.Libyaml     ( Text/Libyaml.hs, .stack-work/dist/x86_64-linux-nix/Cabal- )
[ 2 of 10] Compiling Data.Yaml.Parser ( Data/Yaml/Parser.hs, .stack-work/dist/x86_64-linux-nix/Cabal- )
[ 3 of 10] Compiling Data.Yaml.Internal ( Data/Yaml/Internal.hs, .stack-work/dist/x86_64-linux-nix/Cabal- )
/run/user/1000/ghc25193_0/ghc_30.s: Assembler messages:
/home/shana/programming/yaml//run/user/1000/ghc25193_0/ghc_30.s:67519:0: error:
     Error: can't resolve `.Lc1azh_entry_end' {*UND* section} - `c1azh_entry' {*UND* section}
67519 |         .quad .Lc1azh_entry_end-c1azh_entry
      | ^    
`cc' failed in phase `Assembler'. (Exit code: 1)
Progress: 1/2
--  While building custom Setup.hs for package yaml-0.8.28 using:
      /home/shana/.stack/setup-exe-cache/x86_64-linux-nix/Cabal-simple_mPHDZzAJ_2.0.1.0_ghc-8.2.2 --builddir=.stack-work/dist/x86_64-linux-nix/Cabal- build lib:yaml exe:examples exe:json2yaml exe:yaml2json --ghc-options " -ddump-hi -ddump-to-file -fdiagnostics-color=always"
    Process exited with code: ExitFailure 1                                                                                                                              Completed 2 action(s).
$ uname -a
Linux kagami 4.14.12 #1-NixOS SMP Fri Jan 5 14:48:59 UTC 2018 x86_64 GNU/Linux
#14811 fixed Unary unboxed tuple field causes interface file error dfeuer

Compiling this code under 8.2 or HEAD (but not 8.0), I get an error.

{-# language UnboxedTuples #-}
module Reccy where

data Foo a = Foo (# a #)
Reccy.hs:1:1: error:
    Can't find interface-file declaration for variable GHC.Types.$tcUnit#
      Probable cause: bug in .hi-boot file, or inconsistent .hi file
      Use -ddump-if-trace to get an idea of which file caused the error
1 | -- {-# language GADTs, TypeOperators #-}
  | ^
#14808 fixed GHC HEAD regression: GADT constructors no longer quantify tyvars in topological order RyanGlScott

Originally noticed in #14796. This program:

{-# LANGUAGE ConstraintKinds #-}
{-# LANGUAGE TypeApplications #-}
module Bug where

import Data.Kind

data ECC ctx f a where
  ECC :: ctx => f a -> ECC ctx f a

f :: [()] -> ECC () [] ()
f = ECC @() @[] @()

Typechecks in GHC 8.2.2 and 8.4.1, but not in GHC HEAD:

$ ~/Software/ghc2/inplace/bin/ghc-stage2 Bug.hs
[1 of 1] Compiling Bug              ( Bug.hs, Bug.o )

Bug.hs:12:5: error:
    • Couldn't match type ‘()’ with ‘[]’
      Expected type: [()] -> ECC (() :: Constraint) [] ()
        Actual type: () [] -> ECC (() :: Constraint) () []
    • In the expression: ECC @() @[] @()
      In an equation for ‘f’: f = ECC @() @[] @()
12 | f = ECC @() @[] @()
   |     ^^^^^^^^^^^^^^^

Bug.hs:12:10: error:
    • Expected kind ‘* -> *’, but ‘()’ has kind ‘*’
    • In the type ‘()’
      In the expression: ECC @() @[] @()
      In an equation for ‘f’: f = ECC @() @[] @()
12 | f = ECC @() @[] @()
   |          ^^

Bug.hs:12:14: error:
    • Expecting one more argument to ‘[]’
      Expected a type, but ‘[]’ has kind ‘* -> *’
    • In the type ‘[]’
      In the expression: ECC @() @[] @()
      In an equation for ‘f’: f = ECC @() @[] @()
12 | f = ECC @() @[] @()
   |              ^^

This is because the order of type variables for ECC has changed between GHC 8.4.1 and HEAD. In 8.4.1, it's

$ /opt/ghc/8.4.1/bin/ghci Bug.hs -XTypeApplications -fprint-explicit-foralls
GHCi, version  :? for help
Loaded GHCi configuration from /home/rgscott/.ghci
[1 of 1] Compiling Bug              ( Bug.hs, interpreted )
Ok, one module loaded.
λ> :type +v ECC
  :: forall (ctx :: Constraint) (f :: * -> *) a.
     ctx =>
     f a -> ECC ctx f a

In GHC HEAD, however, it's:

$ ~/Software/ghc2/inplace/bin/ghc-stage2 --interactive Bug.hs -XTypeApplications -fprint-explicit-foralls
GHCi, version 8.5.20180213:  :? for help
Loaded GHCi configuration from /home/rgscott/.ghci
[1 of 1] Compiling Bug              ( Bug.hs, interpreted )
Ok, one module loaded.
λ> :type +v ECC
  :: forall (f :: * -> *) a (ctx :: Constraint).
     ctx =>
     f a -> ECC ctx f a

This regression was introduced in fa29df02a1b0b926afb2525a258172dcbf0ea460 (Refactor ConDecl: Trac #14529).

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. 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