Version 1 (modified by trac, 14 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 was 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 critera 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:

Problems after 12hrs during LAM run
UM ERROR in U_MODEL (error code 4)
devt quota
Start dumps for HECToR run
Error message
Problem with global job for LAM
Processing UM output files to netcdf format
Ensmble run using HiGEM1.2 is doing the job for run member at a time and getting terminated
GHUI errors and warning
Compilation error for UM7.3
"UNRECOVERABLE library error" in makeBC run.
N512 job ported to Monsoon?
error when running umui
UM-UKCA v8.4 ARCHER job xlrfv reconfiguration cannot find STASH section 34-163 in dump (but it's there!)
Setting up ensemble simulations
UKCA job runs for 16 days and then walltime is exceeded
Cannot submit on ARCHER
Problem with a Global Reconfiguration job
Fail to submit a standard job from PUMA
UM parallel running problem
Disk quota increase
Error in buffin errorCode= 3.
Unrecognised in namelist input
vegetation Leaf Area Index (LAI) for each Plant Functional Type (PFT): December anomaly
postproc timeout
Soil Moisture benchmark data and model variable for ILAMB
Reconfiguration failure
Model still failing after this morning's reboot.
um-atmos recon threading levels and defensive checks
Shortcut to saved session
RosePOpenError - Nested Suite Tutorial 2019
Restarting suite
cannot log onto ARCHER account
UM Version 11.5 not available in CMS Helpdesk options
ARCHER work allocation adjustment request

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=1.0|2.0&resolution=duplicate, compact)]]

This is displayed as:

#98, #129, #139, #198, #236, #380, #384, #516, #615, #926, #1470, #1563, #1672, #1717, #1987, #2024, #2093, #2154, #2228, #2254, #2419, #2492, #2500, #2542, #2592, #2639, #2738, #2779, #2926, #2992, #3098, #3105, #3122, #3198, #3321, #3357

Query Language

query: TracLinks and the [[TicketQuery]] macro both use a mini “query language” for specifying query filters. Basically, the filters are separate 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