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:

No results

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

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#92 fixed SALI missing modules dennis dennis
#89 duplicate Cloning error with RAID1 in golden client. somebody anonymous
#87 duplicate Error while booting from PXE and restoring from cloned image. somebody anonymous
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 63)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#92 fixed SALI missing modules dennis dennis
Description

I got a question via twitter that SALI is not working on a Dell 5040 Skylake machine. Currently I'm looking for the missing module.

I got a Dell 7040 (guessing hardware is more or less the same as 5040) and this is de lsmod output:

Module                  Size  Used by
hid_generic            16384  0 
usbhid                 45056  0 
usb_storage            57344  0 
snd_hda_codec_hdmi     49152  1 
dell_led               16384  0 
snd_hda_codec_realtek    65536  1 
snd_hda_codec_generic    65536  1 snd_hda_codec_realtek
sd_mod                 45056  0 
dell_wmi               16384  0 
sparse_keymap          16384  1 dell_wmi
i915                 1138688  2 
dcdbas                 16384  0 
snd_hda_intel          32768  0 
snd_hda_codec         106496  4 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel
drm_kms_helper        106496  1 i915
snd_hda_core           49152  5 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel
ahci                   36864  0 
snd_hwdep              16384  1 snd_hda_codec
libahci                28672  1 ahci
pcspkr                 16384  0 
snd_pcm                90112  4 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_core
e1000e                212992  0 
libata                196608  2 ahci,libahci
serio_raw              16384  0 
snd_timer              28672  1 snd_pcm
xhci_pci               16384  0 
ptp                    20480  1 e1000e
xhci_hcd              159744  1 xhci_pci
snd                    65536  8 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel
pps_core               20480  1 ptp
i2c_i801               20480  0 
scsi_mod              196608  3 usb_storage,libata,sd_mod
drm                   286720  3 i915,drm_kms_helper
soundcore              16384  1 snd
mei_me                 28672  0 
usbcore               196608  4 usb_storage,usbhid,xhci_hcd,xhci_pci
evdev                  24576  0 
mei                    81920  1 mei_me
usb_common             16384  1 usbcore
i2c_algo_bit           16384  1 i915
fan                    16384  0 
thermal                20480  0 
wmi                    20480  2 dell_led,dell_wmi
battery                16384  0 
i2c_hid                20480  0 
hid                   106496  3 i2c_hid,hid_generic,usbhid
video                  36864  2 i915,dell_wmi
i2c_core               49152  6 drm,i915,i2c_i801,i2c_hid,drm_kms_helper,i2c_algo_bit
tpm_tis                20480  0 
tpm                    36864  1 tpm_tis
acpi_pad               24576  0 
button                 16384  1 i915
processor              32768  0 

Investigateing futher.

#89 duplicate Cloning error with RAID1 in golden client. somebody anonymous
Description

Hello,

I have successfully saved golden client image backup in image server. In golden client RAID1 configuration is there.

Partition info...

Device File system mount point size /dev/md0 ext4 /boot 1 GB /dev/md1 swap none 2 GB /dev/md2 ext4 / 200 GB

RAID1 info... md0 : active raid1 sda1[0] sdb1[1] md1 : active raid1 sdb2[1] sda2[0] md2 : active raid1 sdb3[1] sda3[0]

Now when I am trying to clone another client node with same hardware as golden client using master script its given some error messages like bellow. I am using sali kenel and initrd.img for PXE boot.

ERROR ====== mdadm: note: this array has metadata at the start and may not be suitable as a boot device. If you plan to store '/boot' on this device please ensure that your boot-loader understands md/v1.x metadata, or use --metadata=0.90 mdadm: super1.x can not open /dev/sdb1: Device or resource busy mdadm: /dev/sdb1 is not suitable for this array mdadm: create aborted mdadm: cannot open /dev/sda2: Device or resource busy mdadm: cannot open /dev/sda3: Device or resource busy Setting up swapspace version 1, size = 1998516224 bytes UUID=4df53cb2-fe7c-43e6-98al-978e79592ald mke2fs: Device size reported to be zero. Invalid partition specified, or partition table wasn't reread after running fdisk, due to a modified partition being busy and in use. You may need to reboot to re-read your partition table.

I am totally confused here and any help is truly appreciated!

Thannks,

#87 duplicate Error while booting from PXE and restoring from cloned image. somebody anonymous
Description

I am unable to restore previously cloned image to a empty client node. Whenever the client booting from PXE server and trying to collect information about image from image server, its showing some error messages like this...

Retrieving installation data

: : Retrieving scripts directory

rsync: read error : connection reset by peer (104) rsync error : error in rsync protocl data stream (code 12) at io.c(764) [Receiver=3.0.9]

Running pre-install scripts

Installing image ( using the old method )

: : An error has accured, killing of running processes.

I totally clueless here and need your kind help. Please help me on this. I am using sali 1.6.3 server and client version.

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 8 years ago Last modified on 11/19/12 11:28:23