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 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 and no name/email 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 pulldown 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 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

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

Using the [[TicketQuery]] Macro

The TicketQuery macro lets you display lists of tickets matching certain criteria anywhere you can use Wiki Formatting.



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. This also allows displaying the link and description of a single ticket:


This is displayed as:

remove the explicit loop which is not necessary in the computation of [uv]_oce(:,:) arrays

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, use the count parameter.

[[TicketQuery(version=0.6|0.7&resolution=duplicate, count)]]

This is displayed as:


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:


This is displayed as:

Full rows

In table format you can also have full rows by using rows≤field> like below:


This is displayed as:

Results (1 - 3 of 2321)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#2510 fixed out of bound in dtadyn.F90 mathiot mathiot


SETTE tests on the trunk failed on UGA cluster. The failed occurs during the mid year merge.


After running sette in debug mode, it appears there is an out of bound in dtadyn.F90. The use of jf_ubl and jf_vbl need to be protected by ln_trabbl.


  • src/OFF/dtadyn.F90

    295295      CALL fld_fill( sf_dyn, slf_d, cn_dir, 'dta_dyn_init', 'Data in file', 'namdta_dyn' ) 
    296296      sf_dyn(jf_uwd)%cltype = 'U'   ;   sf_dyn(jf_uwd)%zsgn = -1._wp   
    297297      sf_dyn(jf_vwd)%cltype = 'V'   ;   sf_dyn(jf_vwd)%zsgn = -1._wp   
    298       sf_dyn(jf_ubl)%cltype = 'U'   ;   sf_dyn(jf_ubl)%zsgn =  1._wp   
    299       sf_dyn(jf_vbl)%cltype = 'V'   ;   sf_dyn(jf_vbl)%zsgn =  1._wp   
    300298      ! 
     299      IF( ln_trabbl ) THEN 
     300         sf_dyn(jf_ubl)%cltype = 'U'   ;   sf_dyn(jf_ubl)%zsgn =  1._wp   
     301         sf_dyn(jf_vbl)%cltype = 'V'   ;   sf_dyn(jf_vbl)%zsgn =  1._wp   
     302      END IF 
     303      ! 
    301304      ! Open file for each variable to get his number of dimension 
    302305      DO ifpr = 1, jfld 
    303306         CALL fld_def( sf_dyn(ifpr) ) 

How to avoid

  • short term: for every important merge: run sette with debug mode few time step
  • long term: fix sette to do it automatically
#2504 fixed Minor typo in sbc_blk_init that can lead to incorrect reporting of bulk formulation choice acc acc


A simple cut-and-paste error that means the true value of ln_COARE_3p5 is never reported to ocean.output



WRITE(numout,*) '      "COARE 3.5" algorithm   (Edson et al. 2013)         ln_COARE_3p5 = ', ln_COARE_3p0


WRITE(numout,*) '      "COARE 3.5" algorithm   (Edson et al. 2013)         ln_COARE_3p5 = ', ln_COARE_3p5
#2502 fixed DOMcfg: improve reproducibility of the mathiot mathiot


When you found a, it is difficult to know how it has been built and how to reproduce it. MEOM/DRAKKAR build a script to add a specific the namelist_cfg in it as netcdf variable and input file name as attribute. A script to generate the namelist from the is also available.


To partially fix this, namelist_cfg should be introduced in the output file AND bathymetry, coordinate (…) files name used to generate the input file should be added to the namelist_cfg (default name being the one specified in namelist_ref of the domain_cfg).


  • Introduced in the namelist the ability to use non generic name for coordinates, bathy, isf draft:
   cn_fcoord   =  ''             ! external coordinates file (jphgr_msh = 0)
   cn_topo     =  '           '  ! external topo file (nn_bathy =1/2)
   cn_topolvl  =  '           '  ! external topo file (nn_bathy =1) 
   cn_fisfd    =  ''         ! external isf draft (nn_bathy =1 and ln_isfcav = .true.)
   cn_bath     =  'Bathymetry'                 ! topo name in file  (nn_bathy =1/2)
   cn_bathlvl  =  'Bathy_level'                ! lvl name in file   (nn_bathy =1) 
   cn_visfd    =  'isf_draft'                  ! isf draft variable (nn_bathy =1 and ln_isfcav = .true.)
  • Add the sript to include the into the netcdf:
    ./dom_doc.exe -h
      usage : dom_doc -n NAMELIST-file 
                            -d DOMAIN_CFG-file
          PURPOSE :
             Add information in the file after its creation for
             NEMO4. The additional information consists in a new netcdf variable
             called namelist_cfg, holding the content of the used namelist_cfg.
          ARGUMENTS :
             -n NAMELIST-file : name of the namelist_cfg. file required
             -d DOMAIN_CFG-file : name of the domain_cfg file to document. file requ
          OUTPUT : 
              input DOMAIN_CFG-file is modified on output.
  • Add the reverse script (ie to generate the namelist from the namelist_cfg netcdf variable):
    ./xtrac_namelist.bash namelist_output
    (base) mathiotp@f-dahu:.../test_trunk$ cat namelist_output 
    !! NEMO/OCE :   Reference namelist_ref                                !!
    !! NEMO/OCE  :  1 - Domain & run manager (namrun, namcfg, namdom, namzgr, namzgr_sco )
    !!              8 - diagnostics      (namnc4)
    !!             10 - miscellaneous    (nammpp, namctl)
    &namrun        !   parameters of the run
    &namdom        !   space and time domain (bathymetry, mesh, timestep)
       ln_read_cfg = .false.   !  Read from a domain_cfg file
       nn_bathy    =    1      !  compute analyticaly (=0) or read (=1) the bathymetry file
                               !  or compute (2) from external bathymetry
       nn_interp   =    1                          ! type of interpolation (nn_bathy =2)
       cn_domcfg   = ' '       ! Name of the domain_cfg input file
       cn_fcoord   =  ''             ! external coordinates file (nn_bathy =2)
       cn_topo     =  ''             ! external topo file (nn_bathy =2)
       cn_topolvl  =  ''             ! external topo file (nn_bathy =2)
       cn_fisfd    =  ''         ! external isf draft (nn_bathy =2 and ln_isfcav = .true.)
       cn_bath     =  'Bathymetry_isf'             ! topo name in file  (nn_bathy =2)
       cn_visfd    =  'isf_draft'                  ! isf draft variable (nn_bathy =2 and ln_isfcav = .true.)
       cn_lon      =  'nav_lon'                    ! lon  name in file  (nn_bathy =2)
       cn_lat      =  'nav_lat'                    ! lat  name in file  (nn_bathy =2)
       rn_bathy    =    0.     !  value of the bathymetry. if (=0) bottom flat at jpkm1
       nn_msh      =    1      !  create (=1) a mesh file or not (=0)
       rn_hmin     =   10.     !  min depth of the ocean (>0) or min number of ocean level (<0) (out of ice shelf cavity)
       rn_e3zps_min=   20.0     !  partial step thickness is set larger than the minimum of
       rn_e3zps_rat=    0.1    !  rn_e3zps_min and rn_e3zps_rat*e3t, with 0<rn_e3zps_rat<1
       rn_rdt      =  720.0    !  time step for the dynamics (and tracer if nn_acc=0)
       rn_atfp     =    0.1    !  asselin time filter parameter
       ln_crs      = .false.      !  Logical switch for coarsening module
       jphgr_msh   =       2               !  type of horizontal mesh
1 2 3 4 5 6 7 8 9 10 11

Query Language

query: Trac Links 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. 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 left out 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: Trac Tickets, Trac Reports, Trac Guide

Last modified 7 years ago Last modified on 2013-12-24T20:28:30+01:00