| Version 2 (modified by , 13 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.
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.
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 41)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #43 | NoChangeNeeded | trap in netbind using R8169.OS2 | ||
| #42 | fixed | Direct NVETH and E1000E Link | ||
| #41 | fixed | r8169-1.0.0-BETA-20140202 |
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 41)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #43 | NoChangeNeeded | trap in netbind using R8169.OS2 | ||
| Description |
MB asus M5A 78L MLX. In addition to onboard nic I have 1gig Intel nic using your latest driver. Works fine using this: DEVICE=C:\IBMCOM\MACS\E1000E.OS2 DEVICE=C:\IBMCOM\MACS\R8110.OS2 Traps when using this: DEVICE=C:\IBMCOM\MACS\E1000E.OS2 DEVICE=C:\IBMCOM\MACS\R8169.OS2 /V From Pdump: Current slot number: 000d
*000d# 0004 0001 0004 0001 run 0300 f8c0c000 fe226020 f931114c 0f40 00 NETBIND eax=00000081 ebx=00000049 ecx=00000000 edx=00000657 esi=000003f0 edi=000003f0 eip=00000158 esp=0000151e ebp=00001542 iopl=0 -- -- -- nv up ei pl zr na pe nc cs=000f ss=001f ds=001f es=001f fs=150b gs=0000 cr2=00000000 cr3=00000000 p=00 000f:00000158 a11408 mov ax,word ptr [0814] ds:0814=0000 # ========= Nic & driver details: [C:\ibmcom\macs]bldlevel r8169.os2 Build Level Display Facility Version 6.12.675 Sep 25 2001 (C) Copyright IBM Corporation 1993-2001 Signature: @#D Azarewicz:1.0.0#@##1## 16 Feb 2014 10:12:40 DAZAR1 : :::0::SVN27@@Realtek 8169/1Gb PCIe MAC Driver Vendor: D Azarewicz Revision: 1.00.0 Date/Time?: 16 Feb 2014 10:12:40 Build Machine: DAZAR1 FixPak? Version: SVN27 File Version: 1.0 Description: Realtek 8169/1Gb PCIe MAC Driver Bus 2 (PCI Express), Device Number 0, Device Function 0
=========== [C:\ibmcom\macs]bldlevel e1000e.os2 Build Level Display Facility Version 6.12.675 Sep 25 2001 (C) Copyright IBM Corporation 1993-2001 Signature: @#D Azarewicz:0.2.5#@##1## 26 Jan 2014 21:49:21 DAZAR1 : :::5::SVN266@@Intel PRO/1000 PCIe MAC Driver Vendor: D Azarewicz Revision: 0.02.5 Date/Time?: 26 Jan 2014 21:49:21 Build Machine: DAZAR1 FixPak? Version: SVN266 File Version: 0.2.5 Description: Intel PRO/1000 PCIe MAC Driver
======= Further info: Realtek is onboard nic & assigned interface 1 - static IP. Intel is PCIe assigned interface 0 - dhcp IP. Even though I have set up the Realtek I have not plugged in a cable (this will be done when ready to replace old machine). I don't think this matters (and R8110 drivers doesn't trap w/ this setup) but thought it should be mentioned. The assigned IP for lan1 in setup.cmd is rem'd out. bldlevel netbind: Vendor: IBM Revision: 60.58 Date/Time?: Fri May 21 14:12:49 2004 Build Machine: BWBLD254 ASD Feature ID: FixPak? Version: WR_8708 File Version: 60.58 Description: Copyright (c) IBM, 2004 I tried the suggestions at the end of ticket #36 without success. Rgds, jon |
|||
| #42 | fixed | Direct NVETH and E1000E Link | ||
| Description |
Would it be possible to also add a direct download link for the NVETH and E1000E drivers? Like the one for the RTL. IMHO it would make the life a bit easier. |
|||
| #41 | fixed | r8169-1.0.0-BETA-20140202 | ||
| Description |
Hi David, I installed the r8169 beta driver. If i connect to Irc, or connect with FF or with mail all works well. But as soon i use Qbittorrent and i load a torrent file within 15 sec the comps hangs solid. Even the reset button don't work, have to push the on button for 5 sec and then it's rebooting. I don't know if it's relevant but with the multimac driver i had when i download several torrents or nzb files from newsgroups the comp became verry slow, seems the downloads takes all the sources to get it. Sometimes i just had to wait till downloads where done. I have a 150Mbit down and a 10mbit up I attach the trace log and the testlog |
|||
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
