wiki:TracQuery

Version 5 (modified by trac, 22 months ago) (diff)

Trac Ticket Queries

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.

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.

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

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 1863)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#2712 not a bug Outproxy not found curewindow
#2693 fixed Pack200 removal Java 14 zzz zzz
#2686 fixed EventPumper.java: High CPU, leaks memory zzz jogger
1 2 3 4 5 6 7 8 9 10 11

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 1863)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#2712 not a bug Outproxy not found curewindow
Description

I can visit many i2p eepsites as usual. I have green light for tunnels and peers are enough. However, I have received the warning for several weeks when I visit any non-i2p website.

The HTTP Outproxy was not found. It is offline, there is network congestion, or your router is not yet well-integrated with peers. You may want to retry as this will randomly reselect an outproxy from the pool you have defined here (if you have more than one configured). If you continue to have trouble you may want to edit your outproxy list here.

I have set the browser proxy as 127.0.0.1 4444 (http) and 4445(ssl). My HTTP Outproxy: false.i2p, HTTPS Outproxy: outproxy-tor.meeh.i2p. I know that false.i2p is slow. But my i2p used to be fine. The problem took place first when I updated to 0.9.45. I can always visit clearnet such as google via i2p before that. The problem goes on after I deleted i2p totally and reinstalled 0.9.41 and reseeds. I tried several browsers. I configured "Prefer IPv4 over IPv6". I removed the "::1," in the "clientApp.0.args" line, and added "wrapper.java.additional.5=-Djava.net.preferIPv4Stack=true" and "wrapper.java.additional.6=-Djava.net.preferIPv6Addresses=false" as ticket:1400.

ROUTER LOGS: Nothing.

SERVICE (WRAPPER) LOGS INFO: Native CPUID library jcpuid-x86-windows loaded from file INFO: Locally optimized library jbigi-windows-athlon64.dll loaded from file WARN: Configured for 50.00MiBps share bandwidth but only 123.75MiB available memory. Recommend running the restartable version of I2P, and increasing wrapper.java.maxmemory in …\i2p\wrapper.config to at least 140 (MB) if the actual share bandwidth exceeds 512.00KiBps. WARNING: Error starting ConsoleSocket?@……{HTTP/1.1}{::1:7657}: java.net.SocketException?: Address family not supported by protocol family: bind java.net.SocketException?: Address family not supported by protocol family: bind

at sun.nio.ch.Net.bind0(Native Method) at sun.nio.ch.Net.bind(Unknown Source) at sun.nio.ch.Net.bind(Unknown Source) at sun.nio.ch.ServerSocketChannelImpl?.bind(Unknown Source) at sun.nio.ch.ServerSocketAdaptor?.bind(Unknown Source) at org.eclipse.jetty.server.ServerConnector?.open(ServerConnector?.java:321) at org.eclipse.jetty.server.AbstractNetworkConnector?.doStart(AbstractNetworkConnector?.java:80) at org.eclipse.jetty.server.ServerConnector?.doStart(ServerConnector?.java:236) at org.eclipse.jetty.util.component.AbstractLifeCycle?.start(AbstractLifeCycle?.java:68) at net.i2p.router.web.RouterConsoleRunner?.startConsole(RouterConsoleRunner?.java:769) at net.i2p.router.web.RouterConsoleRunner?.startup(RouterConsoleRunner?.java:235) at net.i2p.router.startup.RouterAppManager?.addAndStart(RouterAppManager?.java:54) at net.i2p.router.startup.LoadClientAppsJob?$RunApp?.run(LoadClientAppsJob?.java:301) at java.lang.Thread.run(Unknown Source) at net.i2p.util.I2PThread.run(I2PThread.java:103)

WARNING: Error starting one or more listeners of the Router Console server. If your console is still accessible at http://127.0.0.1:7657/, this may be a problem only with binding to the IPV6 address ::1. If so, you may ignore this error, or remove the "::1," in the "clientApp.0.args" line of the clients.config file.

#2693 fixed Pack200 removal Java 14 zzz zzz
Description

Pack200 deprecated in Java 11 https://openjdk.java.net/jeps/336

Now removed in upcoming Java 14, GA March 2020, already in sid https://openjdk.java.net/jeps/367 https://openjdk.java.net/projects/jdk/14/

Issues are 1) in-net updates; 2) plugins.

1) in-net updates su3 is assumed to contain pack200. Logic in ConfigUpdateHandler? will force update to non-su3, non-torrent HTTP .sud download from stats.i2p or echelon.i2p but we haven't created .sud files since the 0.9.22 release in 2015.

We can stop pack200-ing the update in the release process, and remove the above logic; or create two su3's and torrents and update the above logic and news feed.

2) plugins Only fix is to re-release all plugins without pack200

#2686 fixed EventPumper.java: High CPU, leaks memory zzz jogger
Description

The bug is around runDelayedEvents() looping over _wantsWrite, when closed connections with null _conKey get stuck there forever.

The failsafe code does not catch this. As a quick fix one could loop over _wantsWrite during failsafe to remove closed cons or replace line 821 with

                if ((con = iter.next()).isClosed()) {
                    iter.remove();
                    continue;
                };

Also a list would be more efficient than a hash set. Frequently modified hash maps grow indefinitely large over time even when nearly empty and should be disposed of reqularly.

1 2 3 4 5 6 7 8 9 10 11

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