Trac Ticket Queries
Table of Contents
In addition to reports, Trac provides support for custom ticket queries, which can be used to display tickets that meet specified 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 in and no name/email is 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 dropdown 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 dropdown menu of options can be added multiple times to perform an Or on the criteria.
For text fields such as Keywords and CC the - operator can be used to negate a match and double quotes (since 1.2.1) can be used to match a phrase. For example, a contains match for word1 word2 -word3 "word4 word5" matches tickets containing word1 and word2, not word3 and word4 word5.
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.
After you have edited your filters, click the Update button to refresh your results.
Keyboard shortcuts are available for manipulating the checkbox filters:
- Clicking on a filter row label toggles all checkboxes.
- Pressing the modifier key while clicking on a filter row label inverts the state of all checkboxes.
- Pressing the modifier key while clicking on a checkbox selects the checkbox and deselects all other checkboxes in the filter. Since 1.2.1 this also works for the Columns checkboxes.
The modifier key is platform and browser dependent. On Mac the modified key is Option/Alt or Command. On Linux the modifier key is Ctrl + Alt. Opera on Windows seems to use Ctrl + Alt, while Alt is effective for other Windows browsers.
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.
Note: you must have the REPORT_CREATE permission in order to save queries to the list of default reports. The Save query button will only appear if you are logged in as a user that has been granted this permission. If your account does not have permission to create reports, you can still use the methods below to save a query.
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:
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 in 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 1026)
Full rows
In table format you can also have full rows by 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 1026)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1466 | notabug | Management interface stops working after some time | ||
| Description |
In our solution we are using management interface to authorize clients but after some time (several minutes, few hours) socket stops working - server not sending anything anymore, connection remains established. We've been trying to find the problem for a long time, during this time we have come to certain conclusions:
Example server config: port 1194 proto udp4 dev tun verb 3 # log /tmp/openvpn.log management-hold management-client-auth management-query-passwords auth-user-pass-optional fast-io sndbuf 524288 rcvbuf 524288 cipher none client-to-client keepalive 10 120 tls-server key-direction 0 topology subnet server 10.250.0.0 255.255.0.0 route 10.10.0.0 255.252.0.0 push "topology subnet" push "route 10.10.0.0 255.252.0.0" <tls-auth> ... </tls-auth> <ca> ... </ca> <cert> ... </cert> <key> ... </key> <dh> ... </dh> Code working with management socket after connection sends three lines: bytecount 5 log on hold release Next, only responds to authorize requests (CONNECT/REAUTH) with: client-auth <cid> <kid> END This works for sometime, clients was connected, for each client in 5s intervals BYTECOUNT_CLI was sent by server and suddenly server stops sending BYTECOUNT_CLI and authorize requests. At the time client cannot connect to server: 2022-06-10 03:33:10 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity) 2022-06-10 03:33:10 TLS Error: TLS handshake failed |
|||
| #1465 | fixed | Double-click Tray icon to bring focus to credentials window if displayed | ||
| Description |
When the authentication expires, especially if the computer is asleep, the login dialog box does not pop to the top of the desktop - it is hidden behind other windows. The only visible sign that something is not right is the OpenVPN tray icon is Yellow. Double-clicking on this brings up the status window which does not show any errors. It is only if you then hover over the OpenVPN icon in the Task bar you can see that there are two OpenVPN windows open - the status window and the login box. It would be a really helpful improvement if when you double-click on the tray icon it would first check if the login window is currently displayed, and if so, bring it to the top of the window stack with focus. And, if not, bring up the status box as it does now. Or, if there is a desire to always have the double-click bring the status box up, then in addition to displaying the status box, check if the login box is currently displayed, and bring that into focus over the status box. |
|||
| #1464 | wontfix | Option persist-local-ip does not work | ||
| Description |
Original topic with workaround can be found here. System: Debian 11, OpenVpn? 2.5.1 Server configuration: port 443 dev tun proto tcp-server ifconfig 10.3.4.1 10.3.4.2 secret /etc/openvpn/server-tcp/static.key cipher AES-256-CBC user openvpn group openvpn persist-local-ip persist-key persist-tun status-version 1 mute 20 status /var/log/openvpn/openvpn-tcp-status.log 1 status-version 3 verb 3 Important lines:
Steps to reproduce:
The option persist-local-ip is expected to solve this by re-using previously allocated socket, but it does not. (Similar options persist-key and persist-tun are explicitly mentioned in logs on reset, but not persist-local-ip) Logs: Apr 26 14:14:08 vps systemd[1]: Starting OpenVPN connection to server-tcp... Apr 26 14:14:08 vps ovpn-server-tcp[112347]: Cipher negotiation is disabled since neither P2MP client nor server mode is enabled Apr 26 14:14:08 vps ovpn-server-tcp[112347]: OpenVPN 2.5.1 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on May 14 2021 Apr 26 14:14:08 vps ovpn-server-tcp[112347]: library versions: OpenSSL 1.1.1k 25 Mar 2021, LZO 2.10 Apr 26 14:14:08 vps systemd[1]: Started OpenVPN connection to server-tcp. Apr 26 14:14:08 vps ovpn-server-tcp[112347]: Outgoing Static Key Encryption: Cipher 'AES-256-CBC' initialized with 256 bit key Apr 26 14:14:08 vps ovpn-server-tcp[112347]: Outgoing Static Key Encryption: Using 160 bit message hash 'SHA1' for HMAC authentication Apr 26 14:14:08 vps ovpn-server-tcp[112347]: Incoming Static Key Encryption: Cipher 'AES-256-CBC' initialized with 256 bit key Apr 26 14:14:08 vps ovpn-server-tcp[112347]: Incoming Static Key Encryption: Using 160 bit message hash 'SHA1' for HMAC authentication Apr 26 14:14:08 vps ovpn-server-tcp[112347]: TUN/TAP device tun1 opened Apr 26 14:14:08 vps ovpn-server-tcp[112347]: net_iface_mtu_set: mtu 1500 for tun1 Apr 26 14:14:08 vps ovpn-server-tcp[112347]: net_iface_up: set tun1 up Apr 26 14:14:08 vps ovpn-server-tcp[112347]: net_addr_ptp_v4_add: 10.3.4.1 peer 10.3.4.2 dev tun1 Apr 26 14:14:08 vps ovpn-server-tcp[112347]: Could not determine IPv4/IPv6 protocol. Using AF_INET Apr 26 14:14:08 vps ovpn-server-tcp[112347]: Socket Buffers: R=[131072->131072] S=[16384->16384] Apr 26 14:14:08 vps ovpn-server-tcp[112347]: Listening for incoming TCP connection on [AF_INET][undef]:443 Apr 26 14:23:05 vps ovpn-server-tcp[112347]: TCP connection established with [AF_INET]127.0.0.1:52630 Apr 26 14:23:05 vps ovpn-server-tcp[112347]: TCPv4_SERVER link local (bound): [AF_INET][undef]:443 ### Here openvpn waits for incomming connections ### ### Then I send bad package with nc localhost 443 ### Apr 26 14:23:05 vps ovpn-server-tcp[112347]: TCPv4_SERVER link remote: [AF_INET]127.0.0.1:52630 Apr 26 14:23:05 vps ovpn-server-tcp[112347]: GID set to openvpn Apr 26 14:23:05 vps ovpn-server-tcp[112347]: UID set to openvpn Apr 26 14:23:07 vps ovpn-server-tcp[112347]: WARNING: Bad encapsulated packet length from peer (24947), which must be > 0 and <= 1565 -- please ensure that --tun-mtu or --link-mtu is equal on bot> Apr 26 14:23:07 vps ovpn-server-tcp[112347]: Connection reset, restarting [0] Apr 26 14:23:07 vps ovpn-server-tcp[112347]: SIGUSR1[soft,connection-reset] received, process restarting Apr 26 14:23:07 vps ovpn-server-tcp[112347]: Restart pause, 1 second(s) Apr 26 14:23:08 vps ovpn-server-tcp[112347]: Re-using pre-shared static key Apr 26 14:23:08 vps ovpn-server-tcp[112347]: Preserving previous TUN/TAP instance: tun1 Apr 26 14:23:08 vps ovpn-server-tcp[112347]: Could not determine IPv4/IPv6 protocol. Using AF_INET Apr 26 14:23:08 vps ovpn-server-tcp[112347]: Socket Buffers: R=[131072->131072] S=[16384->16384] Apr 26 14:23:08 vps ovpn-server-tcp[112347]: TCP/UDP: Socket bind failed on local address [AF_INET][undef]:443: Permission denied (errno=13) Apr 26 14:23:08 vps ovpn-server-tcp[112347]: Exiting due to fatal error Apr 26 14:23:08 vps ovpn-server-tcp[112347]: Closing TUN/TAP interface Apr 26 14:23:08 vps ovpn-server-tcp[112347]: net_addr_ptp_v4_del: 10.3.4.1 dev tun1 Apr 26 14:23:08 vps ovpn-server-tcp[112347]: sitnl_send: rtnl: generic error (-1): Operation not permitted Apr 26 14:23:08 vps ovpn-server-tcp[112347]: Linux can't del IP from iface tun1 Apr 26 14:23:08 vps systemd[1]: openvpn@server-tcp.service: Main process exited, code=exited, status=1/FAILURE Apr 26 14:23:08 vps systemd[1]: openvpn@server-tcp.service: Failed with result 'exit-code'. Apr 26 14:23:14 vps systemd[1]: openvpn@server-tcp.service: Scheduled restart job, restart counter is at 84. Apr 26 14:23:14 vps systemd[1]: Stopped OpenVPN connection to server-tcp. |
|||
Query Language
query: TracLinks and the [[TicketQuery]] macro both use a mini “query language” for specifying query filters. Filters are separated by ampersands (&). Each filter 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 |
Filters combining matches and negated matches can be constructed for text fields such as Keywords and CC when using the contains (~=) operator. The - operator is used to negate a match and double quotes (since 1.2.1) are used for whitespace-separated words in a phrase. For example, keywords~=word1 word2 -word3 "word4 word5" matches tickets containing word1 and word2, not word3 and also word4 word5.
status=closed,keywords~=firefox | query closed tickets that contain keyword firefox
|
status=closed,keywords~=opera | query closed tickets that contain keyword opera
|
status=closed,keywords~=firefox opera | query closed tickets that contain keywords firefox and opera
|
status=closed,keywords~=firefox|opera | query closed tickets that contain keywords firefox or opera
|
status=closed,keywords~=firefox,or,keywords~=opera | query closed tickets that contain keyword firefox, or (closed or unclosed) tickets that contain keyword opera
|
status=closed,keywords~=firefox -opera | query closed tickets that contain keyword firefox, but not opera
|
status=closed,keywords~=opera -firefox | query closed tickets that contain keyword opera, but no firefox
|
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 omitted 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 |
Note that modified is the last modified time, so modified with a date range shows ticket that were last modified in that date range. If a ticket was modified in the date range, but modified again after the end date, it will not be included in the results.
See also: TracTickets, TracReports, TracGuide, TicketQuery
