| Version 1 (modified by , 5 years ago) (diff) |
|---|
TicketQuery Wiki Macro
The TicketQuery macro lets you display ticket information anywhere that accepts WikiFormatting.
The query language used by the [[TicketQuery]] macro is described in the TracQuery page.
Usage
[[TicketQuery]]
Wiki macro listing tickets that match certain criteria.
This macro accepts a comma-separated list of keyed parameters, in the form "key=value".
If the key is the name of a field, the value must use the syntax
of a filter specifier as defined in TracQuery#QueryLanguage.
Note that this is not the same as the simplified URL syntax
used for query: links starting with a ? character. Commas (,)
can be included in field values by escaping them with a backslash (\).
Groups of field constraints to be OR-ed together can be separated by a
literal or argument.
In addition to filters, several other named parameters can be used to control how the results are presented. All of them are optional.
The format parameter determines how the list of tickets is
presented:
- list -- the default presentation is to list the ticket ID next to the summary, with each ticket on a separate line.
- compact -- the tickets are presented as a comma-separated list of ticket IDs.
- count -- only the count of matching tickets is displayed
- rawcount -- only the count of matching tickets is displayed, not even with a link to the corresponding query (since 1.1.1)
- table -- a view similar to the custom query view (but without the controls)
- progress -- a view similar to the milestone progress bars
The max parameter can be used to limit the number of tickets shown
(defaults to 0, i.e. no maximum).
The order parameter sets the field used for ordering tickets
(defaults to id).
The desc parameter indicates whether the order of the tickets
should be reversed (defaults to false).
The group parameter sets the field used for grouping tickets
(defaults to not being set).
The groupdesc parameter indicates whether the natural display
order of the groups should be reversed (defaults to false).
The verbose parameter can be set to a true value in order to
get the description for the listed tickets. For table format only.
deprecated in favor of the rows parameter
The rows parameter can be used to specify which field(s) should
be viewed as a row, e.g. rows=description|summary
The col parameter can be used to specify which fields should
be viewed as columns. For table format only.
For compatibility with Trac 0.10, if there's a last positional parameter
given to the macro, it will be used to specify the format.
Also, using "&" as a field separator still works (except for order)
but is deprecated.
Examples
| Example | Result | Macro |
|---|---|---|
| Number of Triage tickets: | 51 | [[TicketQuery(status=new&milestone=,count)]]
|
| Number of new tickets: | 56 | [[TicketQuery(status=new,count)]]
|
| Number of reopened tickets: | 2 | [[TicketQuery(status=reopened,count)]]
|
| Number of assigned tickets: | 6 | [[TicketQuery(status=assigned,count)]]
|
| Number of invalid tickets: | 2 | [[TicketQuery(status=closed,resolution=invalid,count)]]
|
| Number of worksforme tickets: | 0 | [[TicketQuery(status=closed,resolution=worksforme,count)]]
|
| Number of duplicate tickets: | 6 | [[TicketQuery(status=closed,resolution=duplicate,count)]]
|
| Number of wontfix tickets: | 4 | [[TicketQuery(status=closed,resolution=wontfix,count)]]
|
| Number of fixed tickets: | 126 | [[TicketQuery(status=closed,resolution=fixed,count)]]
|
| Number of untriaged tickets (milestone unset): | 59 | [[TicketQuery(status!=closed,milestone=,count)]]
|
| Total number of tickets: | 202 | [[TicketQuery(count)]]
|
| Number of tickets reported or owned by current user: | 0 | [[TicketQuery(reporter=$USER,or,owner=$USER,count)]]
|
| Number of tickets created this month: | 0 | [[TicketQuery(created=thismonth..,count)]]
|
| Number of closed Firefox tickets: | 0 | [[TicketQuery(status=closed,keywords~=firefox,count)]]
|
| Number of closed Opera tickets: | 0 | [[TicketQuery(status=closed,keywords~=opera,count)]]
|
| Number of closed tickets affecting Firefox and Opera: | 0 | [[TicketQuery(status=closed,keywords~=firefox opera,count)]]
|
| Number of closed tickets affecting Firefox or Opera: | 0 | [[TicketQuery(status=closed,keywords~=firefox|opera,count)]]
|
| Number of tickets that affect Firefox or are closed and affect Opera: | 0 | [[TicketQuery(status=closed,keywords~=opera,or,keywords~=firefox,count)]]
|
| Number of closed Firefox tickets that don't affect Opera: | 0 | [[TicketQuery(status=closed,keywords~=firefox -opera,count)]]
|
| Last 3 modified tickets: | #202, #201, #191 | [[TicketQuery(max=3,order=modified,desc=1,compact)]]
|
Details of ticket #1: |
| |
| ||
Format: list
[[TicketQuery(version=0.6|0.7&resolution=duplicate)]]
This is displayed as:
No results
[[TicketQuery(id=123)]]
This is displayed as:
- #123
- Requesting node on shared VLAN results in "resources failed to join" error
Format: compact
[[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]]
This is displayed as:
No results
Format: count
[[TicketQuery(version=0.6|0.7&resolution=duplicate, count)]]
This is displayed as:
Format: progress
[[TicketQuery(milestone=0.12.8&group=type,format=progress)]]
This is displayed as:
Format: table
You can choose the columns displayed in the table format (format=table) using col=<field>. You can specify multiple fields and the order they are displayed 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 138)
Full rows
In table format you can specify full rows 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 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..
|
|||
See also: TracQuery, TracTickets, TracReports
