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

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#815 Done ROMS GIT and SVN Repositories for version control arango
#814 Done IMPORTANT: EcoSim Bio-Optical Diagnostic Terms arango
#813 Fixed Memory Usage Underestimated in Report kate
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 814)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#815 Done ROMS GIT and SVN Repositories for version control arango

ROMS now supports both GIT and SVN version control repositories to check out and update the source code. Both GIT and SVN have their own trac wiki to manage the code and browse updates and bug tracking. However, update or bug trac tickets need to be posted in the SVN trac wiki, for now.

  • GIT URL:
    git clone  MyDir
    git clone  MyDir
    trac:     (no tickets)
  • SVN URL:
    svn checkout --username joe_roms MyDir
    svn checkout MyDir
    svn co MyDir
    trac:         (tickets)

Both repositories use the same username and password selected during ROMS registration. It is a matter of preference what repository system the user selects to managing the code, and we are not recommending which one to use. The ROMS code is identical in both repositories.

For detailed information check WikiROMS pages for GIT and SVN usage:

The code will be updated later to differentiate specific information between GIT and SVN version identifiers like IDs, NetCDF files and standard output metadata, and the Version file.

#814 Done IMPORTANT: EcoSim Bio-Optical Diagnostic Terms arango

Updated the EcoSim model to include diagnostics of the optical terms when DIAGNOSTICS_BIO and BIO_OPTIC to write out into output NetCDF file DIANAME various underwater light spectral properties.

  • The standard input script now has several logical switches to process:
    ! Logical switches (TRUE/FALSE) to activate writing of time-averaged,
    ! underwater optical diagnostics terms into DIAGNOSTIC output file [Ngrids].
      Dout(idSpIr) == T      ! surface_irradiance      surface spectral irradiance
      Dout(iddIrr) == T      ! downward_irradiance     downward spectral irradiance
      Dout(idsIrr) == T      ! scalar_irradiance       scalar spectral irradiance
      Dout(idAcos) == T      ! light_cosine            light spectral average cosine
      Dout(idLatt) == T      ! light_attenuation       diffuse light attenuation
      Dout(idaPHY) == T      ! Phy_absorption          phytoplankton absorption
      Dout(idaDET) == T      ! detrital_absorption     detrital absorption
      Dout(idaCDC) == T      ! CDC_absorption          CDC absorption
      Dout(idsPHY) == T      ! Phy_scattering          phytoplankton scattering
      Dout(idbPHY) == T      ! Phy_backscattering      phytoplankton backscattering
      Dout(idsTOT) == T      ! total_scattering        total scattering
      Dout(idbTOT) == T      ! total_backscattering    total backscattering
  • The varinfo.dat was updated to include the metadata for the new light spectral properties.
  • Added new routines bc_4d.F and exchange_4d.F to process the open boundary conditions for 4D spectral optical fields.
  • If ECOSIM is activated, all output NetCDF files contain the light coordinate for all optical spectral variables:
           double light(Nbands) ;
                   light:long_name = "center wavelength of spectral irradiance bands" ;
                   light:units = "nanometer" ;
    Currently, ECOSIM is configured with 60 wavelenghts of light spectral bands ranging from 402:5:697 nanometers. Notice that all the def_*.F routines that creates ROMS output NetCDF files were updated to include this light coordinate.
  • A new C-preprocessing option BIO_OPTIC is introduced to compute the underwater light spectral properties that are essential for any biogeochemical model. All the EcoSim model routines (ecosim.h, ecosim_def.h, ecosim_inp.h, ecosim_mod.h, ecosim_var.h, and ecosim_wrt.h) were updated.
  • All the changes to the ROMS code were tested with the BIO_TOY test case:

  • The BIO_TOY application was also updated in the test repository. It now includes Matlab script ecosim_optics.m used to generate the above plots.

Many thanks to Bronwyn Cahill for her help coding and testing this update to the EcoSim model.

#813 Fixed Memory Usage Underestimated in Report kate

The dynamic and automatic memory usage is underestimated in the standard output report because of the local variable size2d needs to be bigger in several modules.

We need to have:


instead of

for the horizontal array size.

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 2 years ago Last modified on Jun 20, 2017 2:27:28 PM