wiki:TracQuery

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.

Filters

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:

[[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter)]]

This is displayed as:

Results (1 - 3 of 857)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#858 Done Consolidating public release with research branches arango
#857 Fixed Using increment as subroutine and variable and other updates arango
#856 Done Update for mixed precision computations 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>:

[[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter,rows=description)]]

This is displayed as:

Results (1 - 3 of 857)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#858 Done Consolidating public release with research branches arango
Description

Updated public repository release, so it is synchronized with changes in several of my research branches:

  • Updated mod_netcdf.F to include more information if a reading or writing error occurs. It now has the specific NetCDF library error by using the string from nf90_strerror(status).
  • Changed some of the formatted integer fields to I0. The I0 edit descriptor was introduced in the 2003 Fortran Standard and produce a result with many digits as are necessary to represent the integer value. I love this capability. Well done Fortran Gods!
  • Corrected a small bug in timers.F routine wclocks_off. We need have the following USE statement:
    #ifdef DISTRIBUTE
    !
          USE distribute_mod, ONLY : mp_barrier, mp_reduce
          USE distribute_mod, ONLY : mp_collect
          USE strings_mod,    ONLY : uppercase
    #endif
    
    The mp_collect was restricted to CPP ROMS_STDOUT in a recent update.

Many thanks to Frans van Eeden reporting this issue.

#857 Fixed Using increment as subroutine and variable and other updates arango
Description
  • Corrected a violation to the Fortran standard that doesn't allow to have a subroutine and variable to be named the same. Some Fortran compilers relax that rule. However, gfortran complains. I missed this one. The variable increment is renamed to NLincrement.

Many thanks to Mike Shen for reporting this issue.

  • Corrected segmentation fault in close_io.F when closing the BRY, CLM, and FRC files in the structure. The array index to the files component could go out-of-bounds.
  • Updated timers.F to report the minimum and maximum processes wall CPU time during profiling in distributed-memory applications.
#856 Done Update for mixed precision computations arango
Description
  • The update includes changes to several files to allow mixed single and double precision in some applications. In single precision, we need to ensure that time and scale factors are in double precision. For example, in wrt_ini.F we have:
         real(r8) :: Fmin, Fmax
         real(dp) :: my_time, scale
    
    Recall that in single-precision the floating-point kind parameters are set in mod_kinds.F as:
            integer, parameter :: dp = SELECTED_REAL_KIND(12,300)  ! 64-bit
            integer, parameter :: r4 = SELECTED_REAL_KIND(6,30)    ! 32-bit
    # ifdef SINGLE_PRECISION
            integer, parameter :: r8 = SELECTED_REAL_KIND(6,30)    ! 32-bit
    # else
            integer, parameter :: r8 = SELECTED_REAL_KIND(12,300)  ! 64-bit
    # endif
    
  • Modified routine wclock_off to report also the total profile times in the MPI communications for all nested grids (if NESTING is activated), and its total for all numerical kernels in 4D-Var applications.
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