| Version 2 (modified by , 10 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 filters will display all open tickets, or if you're logged in it will display open tickets assigned to you. Current filters can be removed by clicking the button to the right with the minus sign on the label. New filters are added from the pulldown list in the bottom-right corner of the filters box. 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
While Trac does not yet allow saving a named query and somehow making it available in a navigable list, you can save references to queries in Wiki content, as described below.
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 using 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 138)
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 138)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #198 | fixed | No adminstative/privileged access for ExoGENI rack switches | ||
| Description |
This was missed in testing the GPO and RENCI racks administrative access. Having administrative access to the head node allows user to login to the management and dataplane switches, but does not allows "enable" access (Turn on privileged commands): lnevers@uh-hn ~]$ id uid=2107(lnevers) gid=2000(nonrenci) groups=2000(nonrenci),2501(uhadmins),9510(bbnadmins) [lnevers@uh-hn ~]$ ssh lnevers@uh-8264.uh.xo Enter radius password: IBM Networking Operating System RackSwitch G8264. uh-8264.uh.xo>ena Enable access using (oper) credentials restricted to admin accounts only. uh-8264.uh.xo>exit ... [lnevers@uh-hn ~]$ ssh lnevers@uh-8052.uh.xo Enter radius password: IBM Networking Operating System RackSwitch G8052. uh-8052.uh.xo>ena Enable access using (oper) credentials restricted to admin accounts only. uh-8052.uh.xo> |
|||
| #197 | fixed | ExoSM paths TCP traffic inconsistencies | ||
| Description |
Finding TCP traffic results are inconsistent for site to site connection set up by the ExoSM stitching between the GPO and Houston rack. The following TCP performance was found from GPO EG to Houston EG (repeatable): 1 TCP client = 20.4 Mbits/sec 5 TCP clients = 3.02 Mbits/sec 10 TCP clients = 2.98 Mbits/sec Why does throughput drop from 20 Mbits/sec as more client are added? These are the results for the same requests in the opposite direction from Houston EG to GPO EG: 1 TCP client = 7.95 Mbits/sec 5 TCP clients = 8.81 Mbits/sec 10 TCP clients = 8.66 Mbits/sec Why such low throughput for an ExoSM VLAN? The results above are inconsistent compared to other sites. From GPO EG to UFL EG: 1 TCP client = 27.5 Mbits/sec 5 TCP clients = 139 Mbits/sec 10 TCP clients = 278 Mbits/sec From UFL EG to GPO EG: 1 TCP client = 27.5 Mbits/sec 5 TCP clients = 129 Mbits/sec 10 TCP clients = 201 Mbits/sec |
|||
| #195 | fixed | GENI Network Stitching to Bare Metal nodes does not work. | ||
| Description |
This issue was first reported on Dec 6, 2013. Writing ticket to track to resolution. I just checked to verify the state of this issue and to capture output for this ticket and found that there is now a different failure: Result Summary: Failed CreateSliver for slice IG-ST-4-2pc at https://geni.renci.org:11443/orca/xmlrpc. Error from Aggregate: code 2: ERROR: Exception encountered: java.lang.IndexOutOfBoundsException: Index: 1, Size: 1. Originally, attempts to stitch to bare metal nodes resulted in the following error: 11:16:46 INFO stitch.Aggregate: Stitcher doing createsliver at https://bbn-hn.exogeni.net:11443/orca/xmlrpc
11:16:49 ERROR omni: {'output': 'Embedding workflow ERROR: 4:No Edge Domain Exist:
http://geni-orca.renci.org/owl/c5099b69-099a-4dfa-b89f-11955bce0419#eg-gpo:
http://geni-orca.renci.org/owl/c5099b69-099a-4dfa-b89f-11955bce0419#StitchNode0.\n
Please see https://geni-orca.renci.org/trac/wiki/orca-errors for possible solutions.', 'code': {'geni_code': 2}}
11:16:49 INFO stitch.Aggregate: Got AMAPIError doing createsliver IG-ST-4-2pc at <Aggregate
urn:publicid:IDN+exogeni.net:bbnvmsite+authority+am>: AMAPIError: Error from Aggregate: code 2:
Embedding workflow ERROR: 4:No Edge Domain Exist:
http://geni-orca.renci.org/owl/c5099b69-099a-4dfa-b89f-11955bce0419#eg-gpo:
http://geni-orca.renci.org/owl/c5099b69-099a-4dfa-b89f-11955bce0419#StitchNode0.
Please see https://geni-orca.renci.org/trac/wiki/orca-errors for possible solutions..
|
|||
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.
The available operators are:
= | the field content exactly matches the 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 |
See also: TracTickets, TracReports, TracGuide
