Trac Ticket Queries

Table of Contents

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 filters will display all open tickets, or if you're logged in it will display open tickets assigned to you. Current filters can be removed by clicking the button to the right with the minus sign on the label. New filters are added from the pulldown list in the bottom-right corner of the filters box. 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

While Trac does not yet allow saving a named query and somehow making it available in a navigable list, you can save references to queries in Wiki content, as described below.

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.

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 using 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 260)

Ticket Resolution Summary Owner Reporter
#305 wontfix Order of class declaration in same PHP file moo shumisha
#303 fixed tablesort.js missing from Diagnosis and Coverager moo pierres
#302 wontfix 页面载入初始化优化的建议 moo jonwang

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

Ticket Resolution Summary Owner Reporter
#305 wontfix Order of class declaration in same PHP file moo shumisha

Reported by shumisha, 4 weeks ago.
description

Hi

Some of our customers are having issues running some PHP code on machines running XCache. Don't have exact PHP/XCache versions, as this happens on several machines, but XCache is the common point, and issue appear/Disappear with XCache on/off.

Code is as follow:

<?php $condition = /* some software version condition */ if($condition) {

class myClass extends baseClass {

protected function aMethod($param) {

// do something

}

}

} else {

class myClass extends baseClass {

protected function aMethod( & $param) {

// do something

}

}

}

class baseClass {

}

/** end of file **/

In other words, the baseClass is declared after the top level class extending it.

This is valid PHP code, but with XCache on it fails, PHP throwing a Fatal error: "Class 'baseClass' not found in .....

Can this be fixed please?

Rgds

#303 fixed tablesort.js missing from Diagnosis and Coverager moo pierres

Reported by pierres, 4 weeks ago.
description

tablesort.js is linked from the admin tabs Diagnosis and Coverager, but that file does not exist (at least not in these direcotries)

#302 wontfix 页面载入初始化优化的建议 moo jonwang

Reported by jonwang, 5 weeks ago.
description

我是多年php的开发者，在开发中经常会遇到一个很烦人的问题就是页面在每次请求的时候都会从第一个代码去初始化，然后程序引入框架，读取配置，再快的php框架也敌不过原生php的速度，而现在这年头写php不管是用开源的还是私有的框架，总得加载很多内容，php就在这些做着重复的事情。而现在绝大部分网站都是一个入口文件

既然这样，xcache能否做到这样的功能？ 提供一个方法可以在php的入口index.php的第一行声明启用初始化加速，然后程序在某个地方声明初始化节点完毕。然后xcache会将此时php的内存copy出留作备用，等下一个进程进入时直接把这个内存复制给程序，并且从声明结束处开始下后执行，跳过之前所有代码。 由于是内存的直接复制所以会非常快，这样一个程序就不用反复初始化那些一样的东西了。

不知道明白了么？举个例子： 比如一个我要发100个请帖，如果一个个的写那肯定很慢，那么我写好一个请帖，把被邀请人留空，然后把它扫瞄到电脑上，然后要100个就打印100个，然后把不同的地方填上即可 我的想法就是xcache提供一个声明，将初始化的进程内存缓存下来，然后后面的进程就可以直接复制内存后直接跳过所有的步骤。

如果这个实现了那就牛叉了，我们可以把要include的所有的文件、需要数据库读取的配置等等不变东西的都放在声明里，那样再也不会有人嫌弃框架没有原生的php快了。只要一个初始化加速几乎可以颠覆整个php优化了，那样php就像是一个常驻内存的‘短进程’了

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.

The available operators are:

= the field content exactly matches the 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

See also: TracTickets, TracReports, TracGuide