| Version 2 (modified by , 9 years ago) (diff) |
|---|
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 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.
Navigating Tickets
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.
Using TracLinks
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:
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:
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
- Option DEVISCAN does not work on OpenBSD >= 4.8
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:
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 1257)
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 1257)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1701 | fixed | Smartctl: Exception: json.cpp(313): Assertion failed: p->type == nt_array | ||
| Description |
smartctl -a /dev/da75 --json crashes for one particular disk, perhaps because it has a nonempty pending defects list. [asomers@XXX ~]$ smartctl -V smartctl 7.3 2022-02-28 r5338 [FreeBSD 13.1-XXX amd64] (local build) Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org smartctl comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under the terms of the GNU General Public License; either version 2, or (at your option) any later version. See https://www.gnu.org for further details. smartmontools release 7.3 dated 2022-02-28 at 16:33:40 UTC smartmontools SVN rev 5338 dated 2022-02-28 at 16:34:26 smartmontools build host: amd64-portbld-freebsd13.0 smartmontools build with: C++11, GCC FreeBSD Clang 12.0.1 (git@…:llvm/llvm-project.git llvmorg-12.0.1-0-gfed41342a82f) smartmontools configure arguments: '--disable-dependency-tracking' '--enable-sample' '--with-gnupg=no' '--with-initscriptdir=/usr/local/etc/rc.d' '--with-nvme-devicescan=yes' '--prefix=/usr/local' '--localstatedir=/var' '--mandir=/usr/local/man' '--disable-silent-rules' '--infodir=/usr/local/share/info/' '--build=amd64-portbld-freebsd13.0' 'build_alias=amd64-portbld-freebsd13.0' 'CXX=c++' 'CXXFLAGS=-O2 -pipe -fstack-protector-strong -fno-strict-aliasing ' 'LDFLAGS= -fstack-protector-strong ' 'LIBS=' 'CPPFLAGS=' 'CC=cc' 'CFLAGS=-O2 -pipe -fstack-protector-strong -fno-strict-aliasing ' 'PKG_CONFIG_LIBDIR=/wrkdirs/usr/ports/sysutils/smartmontools/work/.pkgconfig:/usr/local/libdata/pkgconfig:/usr/local/share/pkgconfig:/usr/libdata/pkgconfig' [asomers@XXX ~]$ sudo smartctl -a /dev/da75 --json Smartctl: Exception: json.cpp(313): Assertion failed: p->type == nt_array Please inform smartmontools-support@…, including output of smartctl -V. |
|||
| #1697 | invalid | Question on decoding temperature values from csv file | ||
| Description |
I started looking at the csv files smartd generates and would like some help understanding it. On some websites ATA drives were said to show a 150 offset to the raw value in Celsius. A number 187 would translate to 187-150 as a value for degrees celsius. On some SCSI Enterprise drives the temperature is listed exactly in degrees celsius in the CSV file which is very convenient. I found a few CSV files with strange output and would like to know how to find the correct decoding. Below is some data of ATA drives CSV output searching for then key 194 aka. Temperature_Celsius, showing the column number in which key=194 is found and the min and max value found in the next column that I think is the temperature. For some drives the range can not be linear: minimal value 4, max value 253 would not translate by any linear offset assuming this is a digit and not hex. Also, min=55 max=79 is likely an offset of possibly 100? Pulling with smartctl shows 194 Temperature_Celsius 0x0022 073 046 --- Old_age Always - 27 (Min/Max? 20/46) key=194 in column=35 min=94 max=145 in /tmp/Temperature_Celsius.WD-WMC1T0306391.raw.csv (Model: WDC WD30EZRX-00DC0B0) key=194 in column=41 min=4 max=253 in /tmp/Temperature_Celsius.7SGEWP6C.raw.csv (Model: WDC WD80EFAX-68LHPN0) key=194 in column=53 min=5 max=43 in /tmp/Temperature_Celsius.Z840RT48.raw.csv (Model: ST8000AS0002-1NA17Z) key=194 in column=41 min=4 max=253 in /tmp/Temperature_Celsius.1SG60K6Z.raw.csv (Model: WDC WD80EMAZ-00WJTA0) key=194 in column=53 min=5 max=42 in /tmp/Temperature_Celsius.ZCT0EYFR.raw.csv (Model: ST8000DM004-2CX188) key=194 in column=41 min=104 max=250 in /tmp/Temperature_Celsius.JEGRVHKN.raw.csv (Model: WDC WD100EMAZ-00WJTA0) key=194 in column=53 min=6 max=42 in /tmp/Temperature_Celsius.ZCT0EQG7.raw.csv (Model: ST8000DM004-2CX188) key=194 in column=41 min=181 max=253 in /tmp/Temperature_Celsius.2YHZD7WD.raw.csv (Model: HGST HUH721010ALE601) key=194 in column=50 min=55 max=79 in /tmp/Temperature_Celsius.183584805068.raw.csv (Model: WDC WDS500G2B0A-00SM50) Is there a magic table for each manufacturer to decode the smart output or syntax to log the raw value only? Btw: Google has not been my friend yet in finding an answer. |
|||
| #1696 | fixed | Function ataReadExtSelfTestLog didn't swap byte-order for all little-endian variables on big-endian platform | ||
| Description |
Due this bug, only 1 log entry gets correctly swapped, results in wrong values being displayed on big-endian platforms. For example: # smartctl -l selftest /dev/sdd smartctl pre-7.4 2023-02-12 r5455 [ppc64-linux-4.19.271-rivoreo-powerpc64-largepage] (local build) Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 736 - # 2 Extended offline Aborted by host 90% 736 - # 3 Short offline Completed without error 00% 735 - # 4 Extended offline Aborted by host 90% 50 - # 5 Short offline Completed without error 00% 50 - # 6 Extended offline Completed without error 00% 42 - # smartctl -l xselftest /dev/sdd smartctl pre-7.4 2023-02-12 r5455 [ppc64-linux-4.19.271-rivoreo-powerpc64-largepage] (local build) Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 57346 - # 2 Extended offline Aborted by host 90% 57346 - # 3 Short offline Completed without error 00% 57090 - # 4 Extended offline Aborted by host 90% 12800 - # 5 Short offline Completed without error 00% 12800 - # 6 Extended offline Completed without error 00% 42 - Here the timestamps in the extended self-test log (xselftest) are incorrectly displayed except the last one. |
|||
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
