Version 3 (modified by trac, 9 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 11426)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#15649 duplicate Errors about ambiguous untouchable variable when using constraint variable in RankN type infinity0

The following code compiles and works:

  , FlexibleInstances
  , MultiParamTypeClasses
  , GADTs
  , RankNTypes
  , ScopedTypeVariables
  , UndecidableSuperClasses

import GHC.Types (Constraint)

main :: IO ()
main = do return ()

class (r a) => DynPS r a where
data PSAny r = forall a. DynPS r a => PSAny a

class Unconstrained a
instance Unconstrained a
instance DynPS Unconstrained ()

newtype DynLoad' r = DynLoad' {
  unDynLoad' :: forall ref. r ref => ref -> PSAny r

  :: forall a r . (DynPS r a)
  => DynLoad' r
  -> a -> Maybe a
loadAll loader r = undefined

testCallable :: IO (Maybe ())
testCallable = return $ loadAll (undefined :: DynLoad' Unconstrained) ()

However it's ugly having to expose DynLoad' in the API. Ideally we'd like to have:

  :: forall a r . (DynPS r a)
  => (forall ref. r ref => ref -> PSAny r)
  -> a -> Maybe a
loadAll2 loader r = loadAll (DynLoad' loader :: DynLoad' r) r

But this fails with:

Test3.hs:37:6: error:
    • Couldn't match type ‘r0’ with ‘r’
        ‘r0’ is untouchable
          inside the constraints: r0 ref
          bound by the type signature for:
                     loadAll2 :: forall ref. r0 ref => ref -> PSAny r0
          at Test3.hs:(37,6)-(39,17)
      ‘r’ is a rigid type variable bound by
        the type signature for:
          loadAll2 :: forall a (r :: * -> Constraint).
                      DynPS r a =>
                      (forall ref. r ref => ref -> PSAny r) -> a -> Maybe a
        at Test3.hs:(37,6)-(39,17)
      Expected type: ref -> PSAny r0
        Actual type: ref -> PSAny r
    • In the ambiguity check for ‘loadAll2’
      To defer the ambiguity check to use sites, enable AllowAmbiguousTypes
      In the type signature:
        loadAll2 :: forall a r.
                    (DynPS r a) =>
                    (forall ref. r ref => ref -> PSAny r) -> a -> Maybe a
37 |   :: forall a r . (DynPS r a)
   |      ^^^^^^^^^^^^^^^^^^^^^^^^...

It compiles if we enable AllowAmbiguousTypes, but are then forced to use TypeApplications as well to actually call it. :(

-- as above, but add:
{-# LANGUAGE AllowAmbiguousTypes, TypeApplications #-}

-- and then:

testCallable2 :: IO (Maybe ())
--testCallable2 = return $ loadAll2 (undefined :: forall ref. Unconstrained ref => ref -> PSAny Unconstrained) ()
-- ^ doesn't work either
testCallable2 = return $ loadAll2 @() @Unconstrained undefined ()
#15647 duplicate ghc: panic! (the 'impossible' happened) monomon
ghc: panic! (the 'impossible' happened)
  (GHC version 8.0.2 for x86_64-unknown-linux):
	initTc: unsolved constraints
  WC {wc_insol =
        [W] ask_an9K :: t_an9J[tau:1] (CHoleCan: ask)
        [W] put_an9Q :: t_an9P[tau:1] (CHoleCan: put)}

So this code derives an instance of the Decimal type incorrectly, but not sure if this is causing the error.

I have some nested records, which contain a few Decimals. I am trying to make them acidic.

instance SafeCopy (DecimalRaw a) where
  putCopy (Decimal d) = contain $ safePut d
  getCopy = contain $ Decimal <$> safeGet

deriveSafeCopy 0 'base ''Client
deriveSafeCopy 0 'base ''Article

deriveSafeCopy 0 'base ''ServerData
makeLenses ''ServerData

writeState :: String -> Update ServerData ()
writeState newValue
  = put (ServerData newValue)
queryState :: Update ServerData String
queryState = do ServerData string <- ask
                return string

makeAcidic ''ServerData ['writeState 'queryState]
#15638 fixed Make Ptr argument to hGetBuf and hGetBufSome strict andrewthad

Currently, we have:

hGetBufSome :: Handle -> Ptr a -> Int -> IO Int
hGetBufSome h ptr count = ...

hGetBuf :: Handle -> Ptr a -> Int -> IO Int
hGetBuf h ptr count

I propose putting a bang pattern on the ptr argument to both of these functions. Currently, the non-strictness of this argument causes it to be boxed by functions that call it.

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