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 970)
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 970)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1424 | notabug | --client-disconnect executes after failed --client-connect | ||
| Description |
The Server log: <FAIL> * EasyTLS-client-connect => vars loaded => CN:ss-c-arch => Kill client signal => ==192.168.1.2=1225 => conn_trac_disconnect FAIL => temp-files deleted failed to read generic_ext_md_file 2021-08-21 20:33:40 us=867575 arch/192.168.1.2:1225 WARNING: Failed running command (--client-connect): external program exited with error status: 18 <EXOK> * EasyTLS-client-disconnect => vars loaded => CN:ss-c-arch => X509 serial matched => client_ext_md_file loaded => disconnection success => 88cca7a5b9df705560a0764a427478fe327194ce1d28dd0a6feaf5e797ff5531=650953F06CFC5E2B5B5C4B4820E50D936C90A595=192.168.1.2=1225 => conn_trac_disconnect FAIL => temp-files deleted 2021-08-21 20:33:44 us=53200 arch/192.168.1.2:1225 PUSH: Received control message: 'PUSH_REQUEST' 2021-08-21 20:33:44 us=53309 arch/192.168.1.2:1225 Delayed exit in 5 seconds 2021-08-21 20:33:44 us=53392 arch/192.168.1.2:1225 SENT CONTROL [arch]: 'AUTH_FAILED' (status=1) 2021-08-21 20:33:49 us=614513 arch/192.168.1.2:1225 SIGTERM[soft,delayed-exit] received, client-instance exiting |
|||
| #1409 | fixed | SIGSEGV when server config contains: push "echo" | ||
| Description |
a simple server-side push "echo" without arguments is sufficient to crash all client versions since 4008ce020526f950cb2055ba7effff8f7ceb13e4 (v2.5.1~9) and up to and including at least b7fe49c2f9fe967155960608a029041065c54916 (master branch)
Trivial fix shown below (this is modified code in the ~ line, adding NOTE: I don't know if we need to fix anything in the management code, too, I don't use it currently and can't test. All details in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256331 NOTE: The doc/man-sections/server-options.rst does not list "echo" as pushable! We may want to update documentation on the --push option, too. else if (streq(p[0], "echo") || streq(p[0], "parameter"))
{
struct buffer string = alloc_buf_gc(OPTION_PARM_SIZE, &gc);
int j;
bool good = true;
VERIFY_PERMISSION(OPT_P_ECHO);
for (j = 1; j < MAX_PARMS; ++j)
{
if (!p[j])
{
break;
}
if (j > 1)
{
good &= buf_printf(&string, " ");
}
good &= buf_printf(&string, "%s", p[j]);
}
if (good)
{
/* only message-related ECHO are logged, since other ECHOs
* can potentially include security-sensitive strings */
~ if (p[1] && strncmp(p[1], "msg", 3) == 0)
{
msg(M_INFO, "%s:%s",
pull_mode ? "ECHO-PULL" : "ECHO",
BSTR(&string));
}
#ifdef ENABLE_MANAGEMENT
if (management)
{
management_echo(management, BSTR(&string), pull_mode);
}
#endif
}
|
|||
| #1394 | wontfix | packet loss during duo push request | ||
| Description |
First of all, I'm newbie here and I didn't can found solution to my problem, searching before writing this :) My server runs fine and my clients can connect without problems. Openvpn is installed on a server (OPNSENSE) and I'm doing Authentication certificate + ldap (AD user) + MFA duo in a centOS7 through the plugin duo.
Well, when some users are connected to VPN and other agent wants connect to, the VPN tunnels of the all others clients (previously connected and their tunnels stablished) freezes. I can see how ping to server throught VPN lose atleast 3-5 packets. It's weird. During the analysis I realized that the problem occurs when openvpn sends the push request(duo-phone). As long as the client does not accept the request(duo), everyone in the tunnel loses a packet. we can also say problem may be related to a plugin call auth-user-pass-verify "/usr/local/etc/inc/plugins.inc.d/openvpn/ovpn_auth_verify Attach server conf: cat /var/etc/openvpn/server1.conf dev ovpns1 verb 5 dev-type tun dev-node /dev/tun1 writepid /var/run/openvpn_server1.pid script-security 3 daemon ping-timer-rem persist-key proto tcp-server cipher AES-128-CBC auth SHA256 up /usr/local/etc/inc/plugins.inc.d/openvpn/ovpn-linkup down /usr/local/etc/inc/plugins.inc.d/openvpn/ovpn-linkdown local xxx.xxx.xxx.xxx client-disconnect "/usr/local/etc/inc/plugins.inc.d/openvpn/attributes.sh server1" tls-server server 192.168.xxx.0 255.255.255.0 client-config-dir /var/etc/openvpn-csc/1 auth-user-pass-verify "/usr/local/etc/inc/plugins.inc.d/openvpn/ovpn_auth_verify user 'LDAP_VPN' 'true' 'server1'" via-env tls-verify "/usr/local/etc/inc/plugins.inc.d/openvpn/ovpn_auth_verify tls 'internal-ca' 1" lport 1194 management /var/etc/openvpn/server1.sock unix push "route 10.xxx.0.0 255.xxx.0.0" push "route 172.xxx.0.0 255.xxx.0.0" push "dhcp-option DNS 10.xxx.96.100" push "dhcp-option WINS 10.xxx.96.101" ca /var/etc/openvpn/server1.ca cert /var/etc/openvpn/server1.cert key /var/etc/openvpn/server1.key dh /usr/local/etc/dh-parameters.2048.sample tls-auth /var/etc/openvpn/server1.tls-auth 0 reneg-sec 0 reneg-bytes 0 tcp-queue-limit 512 Attach cient conf: dev tun persist-key proto tcp-client cipher AES-128-CBC auth SHA256 client resolv-retry infinite reneg-sec 0 remote xxxxxxx.com.br 1194 tcp lport 0 verify-x509-name "C=BR, ST=SP, L=SP, O=TI, emailAddress=test@test.com, CN=internal-ca" subject remote-cert-tls server auth-user-pass pkcs12 XXXXXXXXXXXXXXXX.p12 tls-auth XXXXXXXXXXXXXXXXXXXX.key 1 verb 5 Duo auth config [root@ldapproxy01 ~]# cat /opt/duoauthproxy/conf/authproxy.cfg ; Complete documentation about the Duo Auth Proxy can be found here: ; https://duo.com/docs/authproxy_reference ; MAIN: Include this section to specify global configuration options. ; Reference: https://duo.com/docs/authproxy_reference#main-section [main] debug=true ; CLIENTS: Include one or more of the following configuration sections. ; To configure more than one client configuration of the same type, append a ; number to the section name (e.g. [ad_client2]) [ad_client] host=10.XXX.96.101 host_2=10.XXX.96.100 service_account_username=XXXXXXXXXXXX service_account_password=XXXXXXXXXXXXXXX search_dn=DC=TI,DC=intranet ; SERVERS: Include one or more of the following configuration sections. ; To configure more than one server configuration of the same type, append a ; number to the section name (e.g. radius_server_auto1, radius_server_auto2) [ldap_server_auto1] client=ad_client ikey=XXXXXXXXXXXXXXXXXXXX skey=XXXXXXXXXXXXXXXXX api_host=XXXXXXXXXXXXXXXXX failmode=secure exempt_primary_bind=false exempt_ou_1=OU=Users_Application,DC=TI,DC=intranet [root@ldapproxy01 ~]# ovpn_auth_verify #!/bin/sh
if [ "$1" = "tls" ]; then
/usr/local/bin/php /usr/local/etc/inc/plugins.inc.d/openvpn/tls-verify.php -d "$2" "$3"
else
# Single quoting $password breaks getting the value from the variable.
# XXX I really don't like going through openssl for this...
password=$(echo -n "${password}" | /usr/local/bin/openssl enc -base64 | sed -e 's/=/%3D/g')
username=$(echo -n "${username}" | /usr/local/bin/openssl enc -base64 | sed -e 's/=/%3D/g')
/usr/local/bin/php /usr/local/etc/inc/plugins.inc.d/openvpn/auth-user.php "$username" "$password" "$common_name" "$3" "$2" "$4"
fi
exit $?
Client Log: in this line the request of the duo is sent to mobile, if the user does not accept the request on the cell phone, everyone in the tunnel loses package. Wed Mar 17 16:16:51 2021 TCP_CLIENT link remote: [AF_INET]XXX.XXX.XXX.XXX:1194 Wed Mar 17 16:16:48 2021 OpenVPN 2.4.9 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Apr 16 2020
Wed Mar 17 16:16:48 2021 Windows version 6.2 (Windows 8 or greater) 64bit
Wed Mar 17 16:16:48 2021 library versions: OpenSSL 1.1.1f 31 Mar 2020, LZO 2.10
Wed Mar 17 16:16:50 2021 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Wed Mar 17 16:16:50 2021 TCP/UDP: Preserving recently used remote address: [AF_INET]XXX.XXX.XXX.XXX.145:1194
Wed Mar 17 16:16:50 2021 Attempting to establish TCP connection with [AF_INET]XXX.XXX.XXX.XXX:1194 [nonblock]
Wed Mar 17 16:16:51 2021 TCP connection established with [AF_INET]XXX.XXX.XXX.XXX:1194
Wed Mar 17 16:16:51 2021 TCP_CLIENT link local (bound): [AF_INET][undef]:0
Wed Mar 17 16:16:51 2021 TCP_CLIENT link remote: [AF_INET]XXX.XXX.XXX.XXX:1194
Wed Mar 17 16:17:05 2021 [internal-ca] Peer Connection Initiated with [AF_INET]XXX.XXX.XXX.XXX:1194
Wed Mar 17 16:17:06 2021 open_tun
Wed Mar 17 16:17:06 2021 TAP-WIN32 device [Conexão Local] opened: \\.\Global\{XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX}.tap
Wed Mar 17 16:17:06 2021 Notified TAP-Windows driver to set a DHCP IP/netmask of XXX.XXX.XXX.XXX/XXX.XXX.XXX.XXX on interface {xxxxxxxxxxxxxx} [DHCP-serv: XXX.XXX.XXX.XXX, lease-time: 31536000]
Wed Mar 17 16:17:06 2021 Successful ARP Flush on interface [14] {xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx}
Wed Mar 17 16:17:11 2021 Initialization Sequence Completed
Server Log: in this line the request of the duo is sent to mobile, if the user does not accept the request on the cell phone, everyone in the tunnel loses package. Wed Mar 17 16:16:41 2021 TCP_CLIENT link remote: [AF_INET]XXX.XXX.XXX.XXX:1194 Mar 17 16:16:51 OPNsense openvpn[9299]: XXX.XXX.XXX.XXX:53182 peer info: IV_GUI_VER=OpenVPN_GUI_11 Mar 17 16:16:44 OPNsense openvpn[9299]: USERTESTE/XXX.XXX.XXX.XXX:59960 SIGUSR1[soft,connection-reset] received, client-instance restarting Mar 17 16:16:44 OPNsense openvpn[9299]: TCP/UDP: Closing socket Mar 17 16:16:50 OPNsense openvpn[9299]: MULTI: multi_create_instance called Mar 17 16:16:50 OPNsense openvpn[9299]: Re-using SSL/TLS context Mar 17 16:16:50 OPNsense openvpn[9299]: Control Channel MTU parms [ L:1623 D:1170 EF:80 EB:0 ET:0 EL:3 ] Mar 17 16:16:50 OPNsense openvpn[9299]: Data Channel MTU parms [ L:1623 D:1450 EF:123 EB:406 ET:0 EL:3 ] Mar 17 16:16:50 OPNsense openvpn[9299]: Local Options String (VER=V4): 'V4,dev-type tun,link-mtu 1571,tun-mtu 1500,proto TCPv4_SERVER,keydir 0,cipher AES-128-CBC,auth SHA256,keysize 128,tls-auth,key-method 2,tls-server' Mar 17 16:16:50 OPNsense openvpn[9299]: Expected Remote Options String (VER=V4): 'V4,dev-type tun,link-mtu 1571,tun-mtu 1500,proto TCPv4_CLIENT,keydir 1,cipher AES-128-CBC,auth SHA256,keysize 128,tls-auth,key-method 2,tls-client' Mar 17 16:16:50 OPNsense openvpn[9299]: TCP connection established with [AF_INET]XXX.XXX.XXX.XXX:53182 Mar 17 16:16:50 OPNsense openvpn[9299]: TCPv4_SERVER link local: (not bound) Mar 17 16:16:50 OPNsense openvpn[9299]: TCPv4_SERVER link remote: [AF_INET]XXX.XXX.XXX.XXX:53182 Mar 17 16:16:51 OPNsense openvpn[9299]: XXX.XXX.XXX.XXX:53182 TLS: Initial packet from [AF_INET]XXX.XXX.XXX.XXX:53182, sid=0a394370 37da2150 Mar 17 16:16:51 OPNsense openvpn[9299]: XXX.XXX.XXX.XXX:53182 VERIFY SCRIPT OK: depth=0, C=BR, ST=SP, L=SP, O=TI, emailAddress=XXXXXXXXXXXX, CN=USERTESTE Mar 17 16:16:51 OPNsense openvpn[9299]: XXX.XXX.XXX.XXX:53182 VERIFY OK: depth=0, C=BR, ST=SP, L=SP, O=TI, emailAddress=XXXXXXXXXXXXXXX, CN=USERTESTE Mar 17 16:16:51 OPNsense openvpn[9299]: XXX.XXX.XXX.XXX:53182 peer info: IV_VER=2.4.9 Mar 17 16:16:51 OPNsense openvpn[9299]: XXX.XXX.XXX.XXX:53182 peer info: IV_PLAT=win Mar 17 16:16:51 OPNsense openvpn[9299]: XXX.XXX.XXX.XXX:53182 peer info: IV_PROTO=2 Mar 17 16:16:51 OPNsense openvpn[9299]: XXX.XXX.XXX.XXX:53182 peer info: IV_NCP=2 Mar 17 16:16:51 OPNsense openvpn[9299]: XXX.XXX.XXX.XXX:53182 peer info: IV_LZ4=1 Mar 17 16:16:51 OPNsense openvpn[9299]: XXX.XXX.XXX.XXX:53182 peer info: IV_LZ4v2=1 Mar 17 16:16:51 OPNsense openvpn[9299]: XXX.XXX.XXX.XXX:53182 peer info: IV_LZO=1 Mar 17 16:16:51 OPNsense openvpn[9299]: XXX.XXX.XXX.XXX:53182 peer info: IV_COMP_STUB=1 Mar 17 16:16:51 OPNsense openvpn[9299]: XXX.XXX.XXX.XXX:53182 peer info: IV_COMP_STUBv2=1 Mar 17 16:16:51 OPNsense openvpn[9299]: XXX.XXX.XXX.XXX:53182 peer info: IV_TCPNL=1 Mar 17 16:16:51 OPNsense openvpn[9299]: XXX.XXX.XXX.XXX:53182 peer info: IV_GUI_VER=OpenVPN_GUI_11 Mar 17 16:17:05 OPNsense openvpn[23509]: user 'USERTESTE' authenticated using 'LDAP - VPN' Mar 17 16:17:05 OPNsense openvpn[9299]: XXX.XXX.XXX.XXX:53182 TLS: Username/Password authentication succeeded for username 'USERTESTE' Mar 17 16:17:05 OPNsense openvpn[9299]: XXX.XXX.XXX.XXX:53182 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, 2048 bit RSA Mar 17 16:17:05 OPNsense openvpn[9299]: XXX.XXX.XXX.XXX:53182 [USERTESTE] Peer Connection Initiated with [AF_INET]XXX.XXX.XXX.XXX:53182 Mar 17 16:17:05 OPNsense openvpn[9299]: USERTESTE/XXX.XXX.XXX.XXX:53182 MULTI_sva: pool returned IPv4=XXX.XXX.XXX.XXX, IPv6=(Not enabled) Mar 17 16:17:05 OPNsense openvpn[9299]: USERTESTE/XXX.XXX.XXX.XXX:53182 MULTI: Learn: XXX.XXX.XXX.XXX-> USERTESTE/XXX.XXX.XXX.XXX:53182 Mar 17 16:17:05 OPNsense openvpn[9299]: USERTESTE/XXX.XXX.XXX.XXX:53182 MULTI: primary virtual IP for USERTESTE/XXX.XXX.XXX.XXX:53182: XXX.XXX.XXX.XXX Mar 17 16:17:06 OPNsense openvpn[9299]: USERTESTE/XXX.XXX.XXX.XXX:53182 PUSH: Received control message: 'PUSH_REQUEST' Mar 17 16:17:06 OPNsense openvpn[9299]: USERTESTE/XXX.XXX.XXX.XXX:53182 SENT CONTROL [USERTESTE]: 'PUSH_REPLY,route 10.XXX.0.0 255.0.0.0,push-continuation 2' (status=1) Mar 17 16:17:06 OPNsense openvpn[9299]: USERTESTE/XXX.XXX.XXX.XXX:53182 SENT CONTROL [USERTESTE]: 'PUSH_REPLY,route 15.XXX.0.0 255.128.0.0,dhcp-option DOMAIN XXXXXXXXXXXXX,dhcp-option DNS XXX.XXX.XXX.XXX,dhcp-option DNS XXX.XXX.XXX.XXX,dhcp-option WINS XXX.XXX.XXX.XXX,dhcp-option WINS 10.116.96.101,route XXX.XXX.XXX.XXX,topology net30,ifconfig XXX.XXX.XXX.XXX XXX.XXX.XXX.XXX,peer-id 0,cipher AES-256-GCM,push-continuation 1' (status=1) Mar 17 16:17:06 OPNsense openvpn[9299]: USERTESTE/XXX.XXX.XXX.XXX:53182 Data Channel: using negotiated cipher 'AES-256-GCM' Mar 17 16:17:06 OPNsense openvpn[9299]: USERTESTE/XXX.XXX.XXX.XXX:53182 Data Channel MTU parms [ L:1551 D:1450 EF:51 EB:406 ET:0 EL:3 ] Mar 17 16:17:06 OPNsense openvpn[9299]: USERTESTE/XXX.XXX.XXX.XXX:53182 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key Mar 17 16:17:06 OPNsense openvpn[9299]: USERTESTE/XXX.XXX.XXX.XXX:53182 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key |
|||
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
