Trac Ticket Queries
Table of Contents
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.
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:
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:
Results (1 - 3 of 1067)
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 1067)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1427 | fixed | Add support for SCT Error Recovery Timer features added in ACS-4 | ||
| Description |
ATA command set version 4 (ACS-4) and later support new capabilities for the SMART Command Transport (SCT) Error Recovery Control (ERT) function. Specifically, function codes 0003h-0005h were added. These functions are very useful for saving and retrieving persistent-over-power-cycle timer values and for resetting the drive to the manufacturer defaults. The patch provided enables the ability to use these new function codes by extending the functionality of the scterc. The attached patch was generated from the git repo. Let me know if a svn patch is preferred. Usage update:
Man page update:
Usage Examples: 1) Print persistent power-on values jrbauer@zeus:~$ sudo smartctl -l scterc,p /dev/sdb smartctl 7.2 (build date Jan 11 2021) [x86_64-linux-5.4.0-60-generic] (local build) Copyright (C) 2002-21, Bruce Allen, Christian Franke, www.smartmontools.org SCT Error Recovery Control: Power-on Read: Disabled
2) Set power-on values jrbauer@zeus:~$ sudo smartctl -l scterc,80,82,p /dev/sdb smartctl 7.2 (build date Jan 11 2021) [x86_64-linux-5.4.0-60-generic] (local build) Copyright (C) 2002-21, Bruce Allen, Christian Franke, www.smartmontools.org SCT Error Recovery Control set to:
3) Reset power-on and current values to the device default jrbauer@zeus:~$ sudo smartctl -l scterc,r /dev/sdb smartctl 7.2 (build date Jan 11 2021) [x86_64-linux-5.4.0-60-generic] (local build) Copyright (C) 2002-21, Bruce Allen, Christian Franke, www.smartmontools.org SCT Error Recovery Control set to: default values. |
|||
| #1424 | fixed | drivedb.h: Add VERSION information which works without $Id$ expansion | ||
| Description |
In Debian smartmontools#976696, to avoid the monthly debsums cron job complaining that the files in the Debian smartmontools package had been modified after update-smart-drivedb got run, I requested that the Debian maintainer install the drivedb.h from the smartmontools tarball into /usr and then in the postinstall script run at package install time, copy it to the canonical location in /var. The package maintainer implemented that with unconditional copying of the file, with a TODO item to improve that. I noticed that the update-smart-drivedb script also does unconditional copying. The unconditional copying in both the Debian postinstall script and in update-smart-drivedb means that they will both clobber each other's changes. So there needs to be some more sophisticated mechanism to figure out whether or not to update the drivedb.h file. Possibly the branch name plus the revision number or date from the $Id$ expansion could be useful for checking if the drivedb.h file should be updated, however... I noticed that some of the URLs used by the update-smart-drivedb script do not have $Id$ expansion and the drivedb.h on my system downloaded by update-smart-drivedb does not have $Id$ expansion. Also the drivedb.h file within the Debian package does have $Id$ expansion. So if the URLs with missing $Id$ expansion could be fixed or removed, then the branch name plus the revision number or date from the $Id$ expansion could potentially be removed for a version. Alternatively, a manually committed revision number could be added to the file. In addition, I think it would be nice if the Debian package maintainer did not have to re-implement the proposed version checks in the Debian postinstall script, so I suggest that a --local option for update-smart-drivedb could be used to make it look at a local directory for drivedb.h, check the versions and then update the canonical drivedb.h. Then the Debian postinstall script could just run that. I have CCed onlyjob, the Debian package maintainer. |
|||
| #1423 | duplicate | Micron_5300_MTFDDAK480TDS | ||
| Description |
Micron_5300_MTFDDAK480TDS |
|||
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
