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

Ticket Resolution Summary Owner Reporter
#255 fixed reinstall vserver from gentoo to debian -- Markus Petzsch <markus@…>
#249 fixed Problem to install the deamon/ Deamon lässt nsich nicht installieren fLoo David
#248 fixed vserver can't start via webpanel -- speed0815@…

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

Ticket Resolution Summary Owner Reporter
#255 fixed reinstall vserver from gentoo to debian -- Markus Petzsch <markus@…>

Reported by Markus Petzsch <markus@…>, 7 years ago.

description

When reinstalling a vserver from gentoo to debian, the initstyle gets broken.

here is the fix:

in daemon/src/setup.c

exchange line 216 with the following and it works:

strcmp(image.initstyle, "gentoo") == 0 strcmp(image.initstyle, "minit") == 0 strcmp(image.initstyle, "sysv") == 0 )

#249 fixed Problem to install the deamon/ Deamon lässt nsich nicht installieren fLoo David

Reported by David, 8 years ago.

description

Hello Guys, I try to install openvcp deamon. 1. I get openvcpd-0.4rc2.tar.gz and untar it. 2. I configure it. 3. I will use the comand 'make' and 'make install' and here is the problem, it begins and in the end comes an error Message ' make: *** (src/filter.o) Error 1'

I don't now what i have to do???? Can you help me?

Thanks David

;

Hallo, Ich versuche den Deamon von openvcp zu installieren. 1.openvcpd-0.4rc2.tar.gz runtergeladen. 2.configure ausgeführt 3.und das ist das Problem, make bzw. make install ausgeführt. Und bekomme dann diese error Meldung 'make: *** (src/filter.o) Error 1'. Was kann ich dagegen tun??? Ich hoffe ihr könnt mir helfen!

Danke

#248 fixed vserver can't start via webpanel -- speed0815@…

Reported by speed0815@…, 8 years ago.

description

Guten Tag.

Wenn ich einen vServer starten will bekomme ich diesen Error:

secure-mount: write(): Invalid argument
Failed to update mtab-file
secure-mount: write(): Invalid argument
Failed to update mtab-file
vnamespace: vc_set_namespace(): Function not implemented

An error occured while executing the vserver startup sequence; when
there are no other messages, it is very likely that the init-script
(/etc/init.d/rc 3) failed.

Common causes are:
* /etc/rc.d/rc on Fedora Core 1 and RH9 fails always; the 'apt-rpm' build
method knows how to deal with this, but on existing installations,
appending 'true' to this file will help.


Failed to start vserver 'v28001'

hier ein ls -all von /var/lib/vservers/v28001

lynx-lynx@swissvps-lynx-lynx:/vservers$ ls -all v28001/
insgesamt 125312
drwxr-xr-x 19 root      root          4096 2009-05-18 22:13 .
drwxrwxr-x  6 lynx-lynx www-data      4096 2009-08-25 13:50 ..
drwxr-xr-x  2 root      root          4096 2009-05-18 22:14 bin
drwxr-xr-x  2 root      root          4096 2009-05-18 22:12 boot
drwxr-xr-x  4 root      root          4096 2009-05-18 22:14 dev
drwxr-xr-x 71 root      root          4096 2009-08-25 13:51 etc
-rw-r--r--  1 root      root             0 2009-05-18 22:11 fastboot
drwxr-xr-x  2 root      root          4096 2009-05-18 22:12 home
drwxr-xr-x 11 root      root          4096 2009-05-18 22:13 lib
drwxr-xr-x  2 root      root          4096 2009-05-18 22:12 media
drwxr-xr-x  2 root      root          4096 2009-05-18 22:12 mnt
drwxr-xr-x  2 root      root          4096 2009-05-18 22:12 opt
dr-xr-xr-x  2 root      root          4096 2009-08-25 13:51 proc
drwxr-xr-x  2 root      root          4096 2009-05-18 22:12 root
drwxr-xr-x  2 root      root          4096 2009-05-18 22:13 sbin
drwxr-xr-x  2 root      root          4096 2009-05-18 22:12 srv
drwxr-xr-x  2 root      root          4096 2009-05-18 22:12 sys
drwxrwxrwt  2 root      root          4096 2009-05-18 22:14 tmp
-rwxrwxr-x  1 lynx-lynx www-data 128109822 2009-08-24 13:33 ubuntu-8.10-x86.tar.gz
drwxr-xr-x 10 root      root          4096 2009-05-18 22:13 usr
drwxr-xr-x 14 root      root          4096 2009-05-18 22:13 var

was mache ich falsch? kann mir jemand helfen?

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