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

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#2361 invalid Maximum rimwidth text output mathiot mathiot


The maximum rim width evaluated from input file is wrong (below example from SPITZ12 ocean.output):

            read nbit (rec:      1) in ok
            read nbjt (rec:      1) in ok
            read nbrt (rec:      1) in ok
   Maximum rimwidth in file is    694585925
   nn_rimwidth from namelist is            1

This bug does not seem to affect the model solution.


in bdyini, in line ibr_max = MAXVAL( nbrdta(:,igrd,ib_bdy) ), nbrdta in only initialised for nbrdta(1:nblendta(igrd,ib_bdy),igrd,ib_bdy).


  • src/OCE/BDY/bdyini.F90

    422422                  nbrdta(ii,igrd,ib_bdy) = NINT( zz_read(ii,1) ) 
    423423               END DO 
    424424               ! 
    425                ibr_max = MAXVAL( nbrdta(:,igrd,ib_bdy) ) 
     425               ibr_max = MAXVAL( nbrdta(1:nblendta(igrd,ib_bdy),igrd,ib_bdy) ) 
    426426               IF(lwp) WRITE(numout,*) 
    427427               IF(lwp) WRITE(numout,*) ' Maximum rimwidth in file is ', ibr_max 
    428428               IF(lwp) WRITE(numout,*) ' nn_rimwidth from namelist is ', nn_rimwidth(ib_bdy) 
#2360 fixed masking issue in ldftra/ldf_eiv_trp if isf cavities open mathiot mathiot


zpsi_uw and zpsi_vw seems to be defined at WU and WV points instead of U and V points in ldftra/ldf_eiv_trp. The use of u-,v-mask is not an issue as long as there is no ice shelf cavities.


use wumask and wvmask instead of u/v mask.


Change mask in ldftra/ldf_eiv_trp. sette results do not change as expected.

  • src/OCE/LDF/ldftra.F90

    770770         DO jj = 1, jpjm1 
    771771            DO ji = 1, fs_jpim1   ! vector opt. 
    772772               zpsi_uw(ji,jj,jk) = - r1_4 * e2u(ji,jj) * ( wslpi(ji,jj,jk  ) + wslpi(ji+1,jj,jk) )   & 
    773                   &                                    * ( aeiu (ji,jj,jk-1) + aeiu (ji  ,jj,jk) ) * umask(ji,jj,jk) 
     773                  &                                    * ( aeiu (ji,jj,jk-1) + aeiu (ji  ,jj,jk) ) * wumask(ji,jj,jk) 
    774774               zpsi_vw(ji,jj,jk) = - r1_4 * e1v(ji,jj) * ( wslpj(ji,jj,jk  ) + wslpj(ji,jj+1,jk) )   & 
    775                   &                                    * ( aeiv (ji,jj,jk-1) + aeiv (ji,jj  ,jk) ) * vmask(ji,jj,jk) 
     775                  &                                    * ( aeiv (ji,jj,jk-1) + aeiv (ji,jj  ,jk) ) * wvmask(ji,jj,jk) 
    776776            END DO 
    777777         END DO 
    778778      END DO 
#2359 fixed Bug: U/V point interpolation of isf tbl tracer properties mathiot mathiot


Interpolation of the mean tracer properties in the isf top boundary layer on U/V point is wrong.


It only affect the trunk and version 4. Version 3.6 is not affected. A fix has been included 2019 isf development and therefore included in the 2 dev_merge_2019 branches.


  • src/OCE/SBC/sbcisf.F90

    741741      INTEGER ::   ikt, ikb                    ! top and bottom index of the tbl 
    742742      REAL(wp) ::   ze3, zhk 
    743743      REAL(wp), DIMENSION(jpi,jpj) :: zhisf_tbl ! thickness of the tbl 
     744      REAL(wp), DIMENSION(jpi,jpj) :: zvarout 
    744745      !!---------------------------------------------------------------------- 
    746747      ! initialisation 
    749750      SELECT CASE ( cd_ptin ) 
    750751      CASE ( 'U' ) ! compute U in the top boundary layer at T- point  
     752         ! 
     753         zvarout(:,:)=0._wp 
     754         ! 
    751755         DO jj = 1,jpj 
    752756            DO ji = 1,jpi 
    753757               ikt = miku(ji,jj) ; ikb = miku(ji,jj) 
    763767               ! level fully include in the ice shelf boundary layer 
    764768               DO jk = ikt, ikb - 1 
    765769                  ze3 = e3u_n(ji,jj,jk) 
    766                   pvarout(ji,jj) = pvarout(ji,jj) + pvarin(ji,jj,jk) / zhisf_tbl(ji,jj) * ze3 
     770                  zvarout(ji,jj) = zvarout(ji,jj) + pvarin(ji,jj,jk) / zhisf_tbl(ji,jj) * ze3 
    767771               END DO 
    769773               ! level partially include in ice shelf boundary layer  
    770774               zhk = SUM( e3u_n(ji, jj, ikt:ikb - 1)) / zhisf_tbl(ji,jj) 
    771                pvarout(ji,jj) = pvarout(ji,jj) + pvarin(ji,jj,ikb) * (1._wp - zhk) 
     775               zvarout(ji,jj) = zvarout(ji,jj) + pvarin(ji,jj,ikb) * (1._wp - zhk) 
    772776            END DO 
    773777         END DO 
    774778         DO jj = 2, jpj 
    775779            DO ji = 2, jpi 
    776780!!gm a wet-point only average should be used here !!! 
    777                pvarout(ji,jj) = 0.5_wp * (pvarout(ji,jj) + pvarout(ji-1,jj)) 
     781               pvarout(ji,jj) = 0.5_wp * (zvarout(ji,jj) + zvarout(ji-1,jj)) 
    778782            END DO 
    779783         END DO 
    780784         CALL lbc_lnk('sbcisf', pvarout,'T',-1.) 
    782786      CASE ( 'V' ) ! compute V in the top boundary layer at T- point  
     787         ! 
     788         zvarout(:,:)=0._wp 
     789         ! 
    783790         DO jj = 1,jpj 
    784791            DO ji = 1,jpi 
    785792               ikt = mikv(ji,jj) ; ikb = mikv(ji,jj) 
    795802               ! level fully include in the ice shelf boundary layer 
    796803               DO jk = ikt, ikb - 1 
    797804                  ze3 = e3v_n(ji,jj,jk) 
    798                   pvarout(ji,jj) = pvarout(ji,jj) + pvarin(ji,jj,jk) / zhisf_tbl(ji,jj) * ze3 
     805                  zvarout(ji,jj) = zvarout(ji,jj) + pvarin(ji,jj,jk) / zhisf_tbl(ji,jj) * ze3 
    799806               END DO 
    801808               ! level partially include in ice shelf boundary layer  
    802809               zhk = SUM( e3v_n(ji, jj, ikt:ikb - 1)) / zhisf_tbl(ji,jj) 
    803                pvarout(ji,jj) = pvarout(ji,jj) + pvarin(ji,jj,ikb) * (1._wp - zhk) 
     810               zvarout(ji,jj) = zvarout(ji,jj) + pvarin(ji,jj,ikb) * (1._wp - zhk) 
    804811            END DO 
    805812         END DO 
    806813         DO jj = 2, jpj 
    807814            DO ji = 2, jpi 
    808815!!gm a wet-point only average should be used here !!! 
    809                pvarout(ji,jj) = 0.5_wp * (pvarout(ji,jj) + pvarout(ji,jj-1)) 
     816               pvarout(ji,jj) = 0.5_wp * (zvarout(ji,jj) + zvarout(ji,jj-1)) 
    810817            END DO 
    811818         END DO 
    812819         CALL lbc_lnk('sbcisf', pvarout,'T',-1.) 
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 6 years ago Last modified on 2013-12-24T20:28:30+01:00