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.

For text fields such as Keywords and CC the - operator can be used to negate a match and double quotes (since 1.2.1) can be used to match a phrase. For example, a contains match for word1 word2 -word3 "word4 word5" matches tickets containing word1 and word2, not word3 and word4 word5.

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.

Keyboard shortcuts are available for manipulating the checkbox filters:

  • Clicking on a filter row label toggles all checkboxes.
  • Pressing the modifier key while clicking on a filter row label inverts the state of all checkboxes.
  • Pressing the modifier key while clicking on a checkbox selects the checkbox and deselects all other checkboxes in the filter. Since 1.2.1 this also works for the Columns checkboxes.

The modifier key is platform and browser dependent. On Mac the modified key is Option/Alt or Command. On Linux the modifier key is Ctrl + Alt. Opera on Windows seems to use Ctrl + Alt, while Alt is effective for other Windows browsers.

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:

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

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#944 worksforme WD Hard Drive smartd[484]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 102 to 100 Veek
Description

I have been querying my hard disk every 60s for the last few days and plotting temps using hddtemp/rrdtool. It hovers around the 40-42 C mark. https://imgur.com/a/NkIuP

However smartd reports spikes of 100-102 C multiple times per day. I thought this was erroneous BUT when i do

smartctl -a /dev/sda a different picture emerges

194 Temperature_Celsius 0x0022 100 096 000 Old_age Always - 43

WORST shows 96 C which is unusual so I am concluding that smartd is correct after all. However how is it able to detect the spike in temp whereas hddtemp fails?

Is this value (smartd) erroneous? How is it being generated and how accurate is it? Can someone clarify if my temp is spiking to 96 C - could you guys shed some light on how all this works.

(I contacted WD but they just asked me to run some tool of theirs which is not documented very well - i have no idea if their Quick Test is destructive - so I've asked them about that - waiting for their reply)

#943 fixed NetBSD regression in smartmontools 6.6 Alex Samorukov
Description

Smartctl is broken on netbsd/sparc64 (BE) arch

To test if smartctl still works on be i installed NetBSD7.0/sparc64 in the qemu.

It was found that smart support is mostly broken.

bash-4.4# uname -a
NetBSD netbsd 7.0 NetBSD 7.0 (GENERIC.201509250726Z) sparc64
bash-4.4# ./smartctl -d ata /dev/wd0c -A
smartctl 6.7 2017-11-16 r4625 [NetBSD 7.0 sparc64] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

Read SMART Data failed: request failed, error code 0x02

=== START OF READ SMART DATA SECTION ===
bash-4.4# ./smartctl -d ata /dev/wd0c -Ai
smartctl 6.7 2017-11-16 r4625 [NetBSD 7.0 sparc64] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     QEMU HARDDISK
Serial Number:    QM00001
Firmware Version: 2.5+
User Capacity:    5,368,709,120 bytes [5.36 GB]
Sector Size:      512 bytes logical/physical
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ATA/ATAPI-7, ATA/ATAPI-5 published, ANSI NCITS 340-2000
Local Time is:    Sun Nov 19 10:35:54 2017 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

Read SMART Data failed: request failed, error code 0x02

=== START OF READ SMART DATA SECTION ===

At the same time native tool works correctly:

bash-4.4# atactl wd0 smart status
SMART supported, SMART enabled
id value thresh crit collect reliability description                 raw
  1 100    6     yes online  positive    Raw read error rate         0
  3 100    0     yes online  positive    Spin-up time                16
  4 100   20     no  online  positive    Start/stop count            100
  5 100   36     yes online  positive    Reallocated sector count    0
  9 100    0     yes online  positive    Power-on hours count        1
 12 100    0     yes online  positive    Device power cycle count    0
190  69   50     yes online  positive    Airflow Temperature         31 Lifetime min/max 31/0

Links:

Todo:

  1. install NetBSD 7.0 intel to check if bug is BE/sparc specific, check atactl code for the hints.
  2. Check previous smartmontools version (6.5)

Autodetection is broken in smartmontools 6.6/netbsd

sparc64# ./smartctl /dev/wd0c
smartctl 6.7 2017-11-16 r4625 [NetBSD 7.0 sparc64] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

/dev/wd0c: Unable to detect device type
Please specify device type with the -d option.

Use smartctl -h to get a usage summary

Code in the netbsd_smart_interface::autodetect_smart_device(const char * name) is very wrong

#942 fixed add to drivedb: SFCF4096H2BU4TO-I-MS-527-STD Gabriele Pohl
Description

Andreas Bofjäll reported via database mailing list:

Hi,

please add the Swissbit C440 industrial cf card series to the database. Both output from smartctl as well as a patch for drivedb.h are attached (original-* is output from smartctl before patching drivedb.h and the patch is against latest trunk).

It does not support self-tests but has a few custom SMART attributes.

/Andreas

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

Filters combining matches and negated matches can be constructed for text fields such as Keywords and CC when using the contains (~=) operator. The - operator is used to negate a match and double quotes (since 1.2.1) are used for whitespace-separated words in a phrase. For example, keywords~=word1 word2 -word3 "word4 word5" matches tickets containing word1 and word2, not word3 and also word4 word5.

status=closed,keywords~=firefox query closed tickets that contain keyword firefox
status=closed,keywords~=opera query closed tickets that contain keyword opera
status=closed,keywords~=firefox opera query closed tickets that contain keywords firefox and opera
status=closed,keywords~=firefox|opera query closed tickets that contain keywords firefox or opera
status=closed,keywords~=firefox,or,keywords~=opera query closed tickets that contain keyword firefox, or (closed or unclosed) tickets that contain keyword opera
status=closed,keywords~=firefox -opera query closed tickets that contain keyword firefox, but not opera
status=closed,keywords~=opera -firefox query closed tickets that contain keyword opera, but no firefox

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

Note that modified is the last modified time, so modified with a date range shows ticket that were last modified in that date range. If a ticket was modified in the date range, but modified again after the end date, it will not be included in the results.


See also: TracTickets, TracReports, TracGuide, TicketQuery

Last modified 5 weeks ago Last modified on 11/12/2017 01:15:51 PM