wiki:TracQuery

Version 3 (modified by trac, 7 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.

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:

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

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#12644 fixed Lack of instantiation in GHC 8.0.1 simonpj
Description

Consider

{-# LANGUAGE ImpredicativeTypes #-}

data T a = T1 Int

instance Show (T a) where
  show (T1 x) = show x

t1 :: T a
t1 = T1 1

f :: String
f = show t1

This should typecheck fine. The a in data type T is phantom, but we often use phantom types.

But it isn't with GHC 8.0.1:

    • No instance for (Show (forall a. T a))
        arising from a use of ‘show’
    • In the expression: show t1
      In an equation for ‘f’: f = show t1

The problem is in the lack of instantiation of t1 in the argument of show.

Admittedly it only happens with -XImpredicativeTypes, but that flag should never make a legal program fail!

I'm fixing this, but I wanted to make a ticket to exhibit it.

#12641 invalid Indentation works differently for multi-way if than for guards when using comma-separate view patterns ahmadsalim
Description

When trying to parse the following piece of code:

{-# LANGUAGE MultiWayIf #-}
module Test where

data AB = A | B

aAndB :: AB -> AB -> Bool
aAndB ab1 ab2 =
  if | A <- ab1
     , B <- ab2  -> True
     | otherwise -> False

I get the following error

test.hs:9:6: error:
    parse error (possibly incorrect indentation or mismatched brackets)

This is as currently is inconsistent with how guards are parsed, e.g.:

aAndB2 :: AB -> AB -> Bool
aAndB2 ab1 ab2 | A <- ab1
               , B <- ab2 = True
               | otherwise = False

works perfectly fine.

Note, that if I indent the comma a bit in aAndB, the following will parse correctly:

aAndB :: AB -> AB -> Bool
aAndB ab1 ab2 =
  if | A <- ab1
      , B <- ab2  -> True
     | otherwise -> False

Of course, this is far from a major issue, but I thought it would probably be beneficial to report the issue nonetheless. It also looks likely less neat with the comma indented.

#12638 duplicate GHC panic when resolving Show instance MichaelK
Description

I'm playing around with rolling my own type defaulting and found a panic. Note: adding a stub Show (W a) instance resolves this (i.e. show _ = "test").

{- Test.hs -}
{-# LANGUAGE PolyKinds #-}
{-# LANGUAGE TypeFamilies #-}

module Test where

import Data.Proxy

data W (a :: k) = Wk | W (MkStar a)

type family MkStar (a :: k) :: *

main = print (W Proxy :: W (Proxy (~)))
$ ghc Test.hs -o test 
[1 of 1] Compiling Test             ( Test.hs, Test.o )

Test.hs:13:8: error:ghc: panic! (the 'impossible' happened)
  (GHC version 8.0.1 for x86_64-apple-darwin):
	print_equality ~

Please report this as a GHC bug:  http://www.haskell.org/ghc/reportabug

If x = W Proxy :: W (Proxy (~)) is only defined, there is no issue. It seems to occur exactly when resolving a Show instance for W (Proxy (~)) and one does not exist.

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