wiki:TracQuery

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

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#10356 duplicate Couldn't match type ‘a’ with ‘Int’ / ‘a’ is untouchable / inside the constraints () radix
Description

Sadly I'm a Haskell newbie, so this won't be a very good bug report, but I am working on a codebase and I triggered a GHC bug (at least according to GHC itself).

Building json-log-viewer-0.0.1...
Preprocessing executable 'json-log-viewer' for json-log-viewer-0.0.1...
[3 of 3] Compiling Main             ( src/Main.hs, dist/build/json-log-viewer/json-log-viewer-tmp/Main.o )

src/Main.hs:316:41:
    Couldn't match type ‘a’ with ‘Int’
      ‘a’ is untouchable
        inside the constraints ()
        bound by the inferred type of refreshMessages :: IO ()
        at src/Main.hs:(300,7)-(324,48)ghc: panic! (the 'impossible' happened)
  (GHC version 7.10.1 for x86_64-apple-darwin):
	No skolem info: a_al2w[sk]

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

I saved the state of the code in a git branch and put it here: https://github.com/radix/json-log-viewer/tree/ghc-bug

I'll also attach my list of cabal dependencies installed. The only tricky one is that I'm working off of an unreleased version of vty-ui, at this revision: https://github.com/jtdaugherty/vty-ui/commit/c3a0c4b660119a4d5862a6f549a98739a3fc5fa7

I also don't know if the program is "valid" -- I'm in the middle of a refactor, and it's a big cluttered program that I know is very poorly written. Sorry about that. I would not usually report a bug in such a situation but the compiler implored me to, so I am.

#10329 fixed ghc-7.10 is configured to use llvm-3.6 but only compiles with llvm-3.5 erikd
Description

Commit 07da52ce2db1 on the ghc-7.10 branch cherry picks commit 42448e3757f2 from the git master branch, but that commit checks for and insists on using llvm version 3.6. However, the code in the ghc-7.10 branch is not compatible with llvm-3.6.

The attatched patch changes the requirement to be for llvm-3.5 and is the ghc-7.10 version of commit 485dba86d2519c in the master branch.

#10326 wontfix ImpredicativeTypes: Unable to use in Functor etc.. j80JjBjVNRMajmA
Description

I want to use values of RankNTypes within Functors/Monads/... just like normal values.

The following code shows, that I cannot lift a function ReturnNull -> ReturnNull into a functor the way I would like to (e.g. liftId2). However, using another version that seems equivalent and that is allowed by GHC, liftId3, does not allow me to pipe the result to override. How can I do this?

{-# LANGUAGE ImpredicativeTypes #-}

type ReturnNull = forall m. Monad m => m ()

id2 :: ReturnNull -> ReturnNull
id2 = id

testId2 :: ReturnNull
testId2 = id2 $ return ()

liftId :: Functor f => f ReturnNull -> f ReturnNull
liftId = fmap id

-- rejected
liftId2 :: Functor f => f ReturnNull -> f ReturnNull
liftId2 = fmap id2

liftId3 :: (Monad m,Functor f) => f ReturnNull -> f (m ())
liftId3 = fmap id2

override :: Functor f => f ReturnNull -> f ()
override = fmap $ const ()

testLift :: Functor f => f ReturnNull -> f ()
testLift = override . liftId

--rejected
testLift3 :: Functor f => f ReturnNull -> f ()
testLift3 = override . liftId3
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