wiki:TracQuery

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.

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 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 WikiFormatting.

Example:

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

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:

[[TicketQuery(id=123)]]

This is displayed as:

#123
Subcontainers of species can be deleted w/o warning

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:

0

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:

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

This is displayed as:

Results (1 - 3 of 548)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#773 fixed searching '[any field]' does not match fields in sub-containers of DB-items westram westram
#770 handled builds with sanitize+NDEBUG+unittests are painfully slow (esp. with gcc 7.x) westram westram
#769 invalid Problems with RAxML in ARB devel guest
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> like below:

[[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 548)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#773 fixed searching '[any field]' does not match fields in sub-containers of DB-items westram westram
Description

Currently only searches top-level fields.

Defaulting to recursive search is far too slow (because sequence data always is searched)
⇒ add extra pseudo search fields

  • [any recursive]
  • [all recursive]
#770 handled builds with sanitize+NDEBUG+unittests are painfully slow (esp. with gcc 7.x) westram westram
Description

Several modules compile incredibly slow with the above settings:

module buildtime buildmem
gb_aci.cxx 450s 6 Gb (1.3 Gb with 5.5)
insdel.cxx 350s
date.cxx 250s
arb_probe.cxx 170s
PT_buildtree.cxx 140s
ad_cb.cxx 140s
adquery.cxx 100s
Location.cxx 90s

(buildmem for other modules between 1-3 Gb, measured with gcc 7.2)

Functions were marked with comments by [16637]:

  • all affected functions are in unittest code!
  • eliminating these functions does also eliminate the problem

Build times for gcc6.3 are approx. 50-60% of 7.x times.

overall build time:

gcc affected+UT all-UT affected-UT
5.5 9m40s 5m20s 1m
6.3 9m30s 5m20s 1m
7.x 16m30s 6m10s 1m

(UT=unittests, rebuilded affected or all modules)


Problem is caused by optimization.

I tried to disable several optimizations on file- and function-basis using one/some/all of

-fno-var-tracking
-fno-var-tracking-assignments
-fno-gcse
-fno-tree-pta 
-fno-tree-pre
-fno-tree-vectorize
-fno-unit-at-a-time 
-fno-expensive-optimizations

Several did perform slightly better, while overall speed remained more or less the same.

I've also tried to split long test functions into several smaller ones - also no real gain.

#769 invalid Problems with RAxML in ARB devel guest
Description

When ever I try to use RAxML in ARB I have the above error message, can anyone help me? Thank you kind regards

06:36.28 can't load 'RAxML_log.viaARB' (Reason: No such file or directory)

(at /usr/arb/bin/raxml2arb.pl line 51.) Please check console for additional error reasons

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. 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: TracTickets, TracReports, TracGuide

Last modified 2 years ago Last modified on Oct 7, 2015, 2:56:54 PM