wiki:TracQuery

Version 1 (modified by trac, 10 years ago) (diff)

--

Trac Ticket Queries

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.

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 was 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.

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:

Active tickets against 1.0

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:

Assigned tickets by owner

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:

#14
Poor internet access in Convention Room 2
#16
[rt.amsl.com #9750] Convention 1 Wifi is barely 11 mb/sec......
#30
Poor connectivity in Convention2 and 3
#47
Bad access point in Convention 3
#88
[Fwd: Problem: No IP Address]
#176
looks like an AP is misconfig'd?
#243
Re: [79attendees] Problems with ietf-hotel network
#244
Re: [79attendees] Problems with ietf-hotel network
#245
Re: [79attendees] Problems with ietf-hotel network
#303
Audio stream not working in Valley Ballroom A (Transport Area Working Group)
#343
Re: can't reach AS2518
#344
Re: can't reach AS2518
#446
no audio in IPPM / room 253
#451
Opnieuw te bevestigen Internetbankieren Identity
#466
Re: Fwd: Remote participation
#467
http://ietf83streaming.dnsalias.net/ietf/ietf837.m3u (and others?)
#504
Fwd: [www.ietf.org/rt #49828] media stream
#526
Re: IETF 85 - Room 305
#528
Re: IETF 85 - Room 305
#538
Re: ipv6 routing up yet?
#565
1x troubles (fwd)
#572
Broken wired in my room (2433)
#573
No DHCP lease from Tower2 guest room wired connection
#583
Fwd: [www.ietf.org/rt #54682] low audio from Caribbean IV / SIDR
#867
ietf-hotel connection heavy packet losses from the hotel room
#907
trans wg in far east has no working audio
#914
Packet loss on ietf-hotel
#916
Packet loss on ietf-hotel
#925
room network troubles (bad wireless; wired not working at all)
#927
Wireless Issues - Room 3055
#928
Is ietf-hotel stable yet?
#929
IETF Hotel connection is slow and drops frequently
#931
FYI - ietf-hotel very slow in Hilton Prague room 5014
#932
hotel wireless issue
#933
Hotelroom wireless performance issue
#934
Hotel network
#935
Spotty Connection
#936
ietf-hotel network
#937
Re: [93attendees] Fwd: Ethernet cable?
#939
Nexus 10 DNS loss on ietf-hotel
#941
ietf-hotel
#942
Problem with Wifi access ietf-hotel in my Hilton room 6098
#949
Network keeps failing
#961
Significant packet loss on ietf-hotel SSID on L2
#963
hilton guest room problem
#965
room 5083 not wired ?
#966
(new and continued) issues on ietf-hotel
#969
Room wifi
#975
ietf-hotel, public communication
#978
6th floor at the Hilton
#1171
ietf-nat64 does not work on Pixel 2
#1179
Having problems with nat64 SSID
#1186
ietf-NAT64 no route
#1240
v6 advertised on ietf-hotel but doesn't work?
#1245
Message Received: (IPE-Ticket #779210) Notice of Infringement from 31.133.149.214 – Case No. 83f22e52c31e377abe2e

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:

#14, #16, #30, #47, #88, #176, #243, #244, #245, #303, #343, #344, #446, #451, #466, #467, #504, #526, #528, #538, #565, #572, #573, #583, #867, #907, #914, #916, #925, #927, #928, #929, #931, #932, #933, #934, #935, #936, #937, #939, #941, #942, #949, #961, #963, #965, #966, #969, #975, #978, #1171, #1179, #1186, #1240, #1245

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:

55

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