Trac Ticket Queries

In addition to reports, Trac provides support for custom ticket queries, which can be used to display tickets that meet specified 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 filter will display tickets relevant to you:

  • If logged in then all open tickets, it will display open tickets assigned to you.
  • If not logged in but you have specified a name or email address in the preferences, then it will display all open tickets where your email (or name if email not defined) is in the CC list.
  • If not logged in and no name/email is defined in the preferences, then all open issues are displayed.

Current filters can be removed by clicking the button to the left with the minus sign on the label. New filters are added from the dropdown lists at the bottom corners of the filters box; 'And' conditions on the left, 'Or' conditions on the right. Filters with either a text box or a dropdown menu of options can be added multiple times to perform an Or on 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.

After you have 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

Trac allows you to save the query as a named query accessible from the reports module. To save a query ensure that you have Updated the view and then click the Save query button displayed beneath the results. You can also save references to queries in Wiki content, as described below.

Note: one way to easily build queries like the ones below, you can build and test the queries in the Custom report module and when ready - click Save query. This will build the query string for you. All you need to do is remove the extra line breaks.

Note: you must have the REPORT_CREATE permission in order to save queries to the list of default reports. The Save query button will only appear if you are logged in as a user that has been granted this permission. If your account does not have permission to create reports, you can still use the methods below to save a query.

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

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 in by placing pipes (|) between the columns:


This is displayed as:

Results (1 - 3 of 874)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#875 Done IMPORTANT: Compiling ROMS with CMake arango
#874 Done IMPORTANT: Usage of __FILE__ macro arango
#873 Fixed VERY IMPORTANT: Corrected usage of DIURNAL_SRFLUX in 4D-Var arango
1 2 3 4 5 6 7 8 9 10 11

Full rows

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


This is displayed as:

Results (1 - 3 of 874)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#875 Done IMPORTANT: Compiling ROMS with CMake arango

Added the capability to compile ROMS with CMake and ecbuild. We are currently working on the interface to connect ROMS with the Joint Effort for Data Assimilation Integration ​(JEDI) project that is being developed by the Joint Center for Satellite Data Assimilation (JCSDA).

The JEDI layer is model agnostic and includes OOPS (Object-Oriented Prediction System), UFO (Unified Forward Operator), IODA (Interface for Observation Data Access), and other packages for generic applications of data assimilation.

We started working on the roms-jedi repository inside JCSDA GitHub project. To facilitate interactions with all the JEDI packages, we need to have an option to compile ROMS with CMake and ecbuild.

CMake is not as friendly, advanced, and flexible as compiling ROMS with GNU make (gmake). It took David Robertson several weeks to develop a robust and generic strategy to compile and link the various algorithms available in ROMS. The Fortran dependencies were a nightmare because of all the C-preprocessing options in ROMS.

What Is New:

  • Now, there is a CMakeLists.txt in every ROMS source code sub-directory. The top-level CMakeLists.txt in the root directory (same place where GNU makefile is located) contains all the CMake definitions. Also, the Compilers sub-directory includes several .cmake extension configurations files.
  • Two additional build scripts cbuild_roms.csh and were added to ROMS/Bin.
  • A Perl script was added to ROMS/Bin to remove .F files the compiler dependency information when using CMake. The dependency generator is easily confused by CPP if-directives. Only the preprocesed .f90 files are used to determine the dependencies.
  • WARNING: this version of CMake uses ecbuild developed at ECMWF, which consists of a set of macros as well as a wrapper around CMake. It can be downloaded from GitHub. For tutorial and usage check its documentation.

Many thanks to David Robertson for his persistence and making CMake work in ROMS.

#874 Done IMPORTANT: Usage of __FILE__ macro arango

This update modifies the usage of C-preprocessing macro __FILE__, which expands to the name of the current input file being processed. It is an extensive and simple change to ROMS that facilitates the compiling with Cmake in the future.

Now, we define the local variable MyFile as:

     character (len=*), parameter :: MyFile =                          &
    &  __FILE__

So the current filename can expand beyond the 72 columns and compiled free-form compiler flags to avoid syntax errors. It cleans the code substantially.

Usually, MyFile is used in statements like:

     IF (FoundError(exit_flag, NoError, __LINE__, MyFile)) RETURN

     CALL wclock_on (ng, iNLM, 35, __LINE__, MyFile)

     CALL wclock_off (ng, iNLM, 35, __LINE__, MyFile)

These changes are part of several sequential updates to facilitate ROMS interface with Joint Effort for Data Assimilation Integration (JEDI) project.

#873 Fixed VERY IMPORTANT: Corrected usage of DIURNAL_SRFLUX in 4D-Var arango

Corrected a bug in the 4D-Var algorithms when DIURNAL_SRFLUX, FORWARD_FLUXES, and PRIOR_BULK_FLUXES are activated.

Recall that the DIURNAL_SRFLUX option is used to modulate the diurnal cycle to input daily-averaged shortwave radiation flux data. In the adjoint-based algorithms, the FORWARD_FLUXES option is used to process surface fluxes for the tangent linear, representers, and adjoint models from the nonlinear model background trajectory stored in the quicksave (QCK) NetCDF file. See src:ticket:869 for more information. The PRIOR_BULK_FLUXES option is used to impose the initial background trajectory (prior) surface forcing fields stored in QCK in subsequent outer-loops (Nouter>1) and the analysis phase, as also explained in src:ticket:869.

The routines set_data.F, tl_set_data.F, rp_set_data.F, and ad_set_data.F were corrected to avoid modulating the shortwave radiation diurnal cycle when the above options are activated.

In tl_set_data.F, rp_set_data.F, and ad_set_data.F we now have:

#   if defined DIURNAL_SRFLUX && !defined FORWARD_FLUXES
!  Modulate the averaged shortwave radiation flux by the local diurnal
!  cycle.
      CALL ana_srflux (ng, tile, iTLM)
#   endif

while in set_data.F we get:

!  Modulate the averaged shortwave radiation flux by the local diurnal
!  cycle.
      IF (Lprocess) THEN
        CALL ana_srflux (ng, tile, iNLM)
      END IF
#   endif

These changes are necessary to avoid increasing the shortwave radiation values in other 4D-Var outer-loops and the analysis step.

Many thanks to Julia Levin and Gordon Zhang for bringing this problem to our attention.

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. Filters are separated by ampersands (&). Each filter 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. To include a literal & or | in a value, escape the character with a backslash (\).

The available operators are:

= the field content exactly matches 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

The date fields created and modified can be constrained by using the = operator and specifying a value containing two dates separated by two dots (..). Either end of the date range can be left empty, meaning that the corresponding end of the range is open. The date parser understands a few natural date specifications like "3 weeks ago", "last month" and "now", as well as Bugzilla-style date specifications like "1d", "2w", "3m" or "4y" for 1 day, 2 weeks, 3 months and 4 years, respectively. Spaces in date specifications can be omitted to avoid having to quote the query string.

created=2007-01-01..2008-01-01 query tickets created in 2007
created=lastmonth..thismonth query tickets created during the previous month
modified=1weekago.. query tickets that have been modified in the last week
modified=..30daysago query tickets that have been inactive for the last 30 days

See also: TracTickets, TracReports, TracGuide, TicketQuery

Last modified 3 years ago Last modified on Jun 20, 2017 2:27:28 PM