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:
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 107)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #141 | fixed | SIP "BYE" PROBLEM | support@ag-projects.com | oparidae |
| #140 | fixed | Sample code broken by last release | support@ag-projects.com | jcassee |
| #139 | implemented | Support for Python 2.7 | support@ag-projects.com | adigeo |
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 107)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #141 | fixed | SIP "BYE" PROBLEM | support@ag-projects.com | oparidae |
| Description |
I'm quite happy with the overall lib, I only have the following situation in my local AVAYA SIP network, can you try to replicate this?: agents: A - BLINK APPLICATION using sipsimple B - VOIP PHONE/OR ANY SOFTPHONE scenario: 1- I Dial from A TO B, B ANSWERS, wait.. I TERMINATE A, B TERMINATES 2- I Dial from B TO A, A ANSWERS, wait.. I TERMINATE A, B (DOES NOT TERMINATE!!) BLINK SIP TRACE ON scenario 1: (OK CASE) ###############################START OF FILE SCENARIO 1 2011-08-02 14:49:42.461945 [blink 2562]: SENDING: Packet 33, +0:00:15.439867 10.228.88.102:47341 -(SIP over UDP)-> 10.130.0.80:5060 BYE sip:10.130.0.80:6001;transport=tls SIP/2.0 Via: SIP/2.0/UDP 10.228.88.102:47341;rport;branch=z9hG4bKPjP3.EibnifNhJDPgthaJnYZgf1u9ChY2N Max-Forwards: 70 From: "9019805" <sip:9019805@10.130.0.80>;tag=awzR5HikRfYkqAWq0IUKDQ2XMZaCqAFX To: <sip:9019000@10.130.0.80>;tag=80402187ed1e01be144e37a79200 Call-ID: eX8zaQ46hsgL3vQaySY5Zi1cSB5TA4ry CSeq: 3447 BYE Route: <sip:10.130.0.80:5060;lr> Route: <sip:10.130.0.80:6001;transport=tls;lr> User-Agent: Blink 0.2.8 (Linux) Content-Length: 0 -- 2011-08-02 14:49:42.466959 [blink 2562]: RECEIVED: Packet 34, +0:00:15.444881 10.130.0.80:5060 -(SIP over UDP)-> 10.228.88.102:47341 SIP/2.0 407 Proxy Authentication Required From: "9019805" <sip:9019805@10.130.0.80>;tag=awzR5HikRfYkqAWq0IUKDQ2XMZaCqAFX To: <sip:9019000@10.130.0.80>;tag=80402187ed1e01be144e37a79200 Call-ID: eX8zaQ46hsgL3vQaySY5Zi1cSB5TA4ry CSeq: 3447 BYE Via: SIP/2.0/UDP 10.228.88.102:47341;received=10.228.88.102;rport=47341;branch=z9hG4bKPjP3.EibnifNhJDPgthaJnYZgf1u9ChY2N Content-Length: 0 Proxy-Authenticate: Digest realm="rtenergia.pt",domain="rtenergia.pt",nonce="MTMxMjI5MDA0NDpTREZTZXJ2ZXJTZWNyZXRLZXk6MzY5NTMyODA5",algorithm=MD5 Server: Avaya SIP Enablement Services Organization: rtenergia.pt -- 2011-08-02 14:49:42.467153 [blink 2562]: SENDING: Packet 35, +0:00:15.445075 10.228.88.102:47341 -(SIP over UDP)-> 10.130.0.80:5060 BYE sip:10.130.0.80:6001;transport=tls SIP/2.0 Via: SIP/2.0/UDP 10.228.88.102:47341;rport;branch=z9hG4bKPjasYrYTBh9J.WId8LOqSo4yE-soEVaAGq Max-Forwards: 70 From: "9019805" <sip:9019805@10.130.0.80>;tag=awzR5HikRfYkqAWq0IUKDQ2XMZaCqAFX To: <sip:9019000@10.130.0.80>;tag=80402187ed1e01be144e37a79200 Call-ID: eX8zaQ46hsgL3vQaySY5Zi1cSB5TA4ry CSeq: 3448 BYE Route: <sip:10.130.0.80:5060;lr> Route: <sip:10.130.0.80:6001;transport=tls;lr> User-Agent: Blink 0.2.8 (Linux) Proxy-Authorization: Digest username="9019805", realm="rtenergia.pt", nonce="MTMxMjI5MDA0NDpTREZTZXJ2ZXJTZWNyZXRLZXk6MzY5NTMyODA5", uri="sip:10.130.0.80:6001;transport=tls", response="87786e909c16db200b153d12c59c2c9e", algorithm=MD5 Content-Length: 0 -- 2011-08-02 14:49:42.485327 [blink 2562]: RECEIVED: Packet 36, +0:00:15.463249 10.130.0.80:5060 -(SIP over UDP)-> 10.228.88.102:47341 SIP/2.0 200 OK From: "9019805" <sip:9019805@10.130.0.80>;tag=awzR5HikRfYkqAWq0IUKDQ2XMZaCqAFX To: <sip:9019000@10.130.0.80>;tag=80402187ed1e01be144e37a79200 Call-ID: eX8zaQ46hsgL3vQaySY5Zi1cSB5TA4ry CSeq: 3448 BYE Via: SIP/2.0/UDP 10.228.88.102:47341;psrrposn=1;received=10.228.88.102;rport=47341;branch=z9hG4bKPjasYrYTBh9J.WId8LOqSo4yE-soEVaAGq Server: Avaya CM/R015x.02.0.947.3 Content-Length: 0 ###############################END OF FILE SCENARIO 1 BLINK SIP TRACE ON scenario 2: (NOK CASE) ###############################START OF FILE SCENARIO 2 2011-08-02 14:50:26.875594 [blink 2590]: SENDING: Packet 23, +0:00:08.272589 10.228.88.102:33416 -(SIP over UDP)-> 10.130.0.80:5060 BYE sip:9019000@10.130.0.80:6001;transport=tls SIP/2.0 Via: SIP/2.0/UDP 10.228.88.102:33416;rport;branch=z9hG4bKPjXlZEVlaxaBO-26YvcNHRhsry6OAqYLXm Max-Forwards: 70 From: "9019805" <sip:9019805@rtenergia.pt>;tag=d.NACydrdhbyukxBTOoogOjykFRXuYCo To: "ST Travagem" <sip:9019000@rtenergia.pt>;tag=80789e347ed1e01cc144e37a79200 Call-ID: 80789e347ed1e01cd144e37a79200 CSeq: 13051 BYE Route: <sip:10.130.0.80:5060;lr> Route: <sip:10.130.0.80:6001;transport=tls;lr> User-Agent: Blink 0.2.8 (Linux) Content-Length: 0 -- 2011-08-02 14:50:26.880305 [blink 2590]: RECEIVED: Packet 24, +0:00:08.277300 10.130.0.80:5060 -(SIP over UDP)-> 10.228.88.102:33416 SIP/2.0 407 Proxy Authentication Required From: "9019805" <sip:9019805@rtenergia.pt>;tag=d.NACydrdhbyukxBTOoogOjykFRXuYCo To: "ST Travagem" <sip:9019000@rtenergia.pt>;tag=80789e347ed1e01cc144e37a79200 Call-ID: 80789e347ed1e01cd144e37a79200 CSeq: 13051 BYE Via: SIP/2.0/UDP 10.228.88.102:33416;received=10.228.88.102;rport=33416;branch=z9hG4bKPjXlZEVlaxaBO-26YvcNHRhsry6OAqYLXm Content-Length: 0 Proxy-Authenticate: Digest realm="rtenergia.pt",domain="rtenergia.pt",nonce="MTMxMjI5MDA4ODpTREZTZXJ2ZXJTZWNyZXRLZXk6MjAwMjE1MDY5Mw==",algorithm=MD5 Server: Avaya SIP Enablement Services Organization: rtenergia.pt ###############################END OF FILE SCENARIO 2 |
|||
| #140 | fixed | Sample code broken by last release | support@ag-projects.com | jcassee |
| Description |
The sample code at SipSessionExample is broken by the latest release. The parameter to the start method is no longer a configuration instance, but a storage instance. |
|||
| #139 | implemented | Support for Python 2.7 | support@ag-projects.com | adigeo |
| Description |
Refactor code to work with Python 2.7 and Cython interpreter 0.14 |
|||
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
