wiki:TracQuery

Version 4 (modified by trac, 4 years 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 pulldown 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 pulldown menu of options can be added multiple times to perform an Or on 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.

After you have 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 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 1654)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#2444 fixed i2p.i2p revision 3d3b2e109ba3b379ed9f13920fa34d21de0e2b7b fails at `ant i2psnark` step due theme files which were removed zzz slumlord
#2442 invalid Option to disable SSU Peer Test zzz zab
#2437 fixed issues on translated webpage: Unexpected section title or transition slumlord echelon
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 1654)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#2444 fixed i2p.i2p revision 3d3b2e109ba3b379ed9f13920fa34d21de0e2b7b fails at `ant i2psnark` step due theme files which were removed zzz slumlord
Description

Log:

standalone_war:
    [mkdir] Created dir: /usr/home/jenkins/BUiLD/i2p.i2p/apps/i2psnark/java/build/standalone-resources/.resources/themes/snark
     [copy] Copying 278 files to /usr/home/jenkins/BUiLD/i2p.i2p/apps/i2psnark/java/build/standalone-resources/.resources/themes/snark
  [replace] Replaced 0 occurrences in 0 files.
  [replace] Replaced 21 occurrences in 2 files.
  [replace] Replaced 0 occurrences in 0 files.
  [replace] Replaced 2 occurrences in 1 files.
  [replace] Replaced 1 occurrences in 1 files.
  [replace] Replaced 4 occurrences in 4 files.
     [copy] Copying 1 file to /usr/home/jenkins/BUiLD/i2p.i2p/apps/i2psnark/java/build/standalone-resources/.resources/themes/snark/ubergine/images
     [copy] Copying 1 file to /usr/home/jenkins/BUiLD/i2p.i2p/apps/i2psnark/java/build/standalone-resources/.resources/themes/snark/dark/images
     [copy] Copying 1 file to /usr/home/jenkins/BUiLD/i2p.i2p/apps/i2psnark/java/build/standalone-resources/.resources/themes/snark/light/images
     [copy] Copying 1 file to /usr/home/jenkins/BUiLD/i2p.i2p/apps/i2psnark/java/build/standalone-resources/.resources/themes/snark/dark/images
     [copy] Copying 1 file to /usr/home/jenkins/BUiLD/i2p.i2p/apps/i2psnark/java/build/standalone-resources/.resources/themes/snark/ubergine/images

BUILD FAILED
/usr/home/jenkins/BUiLD/i2p.i2p/build.xml:2051: The following error occurred while executing this line:
/usr/home/jenkins/BUiLD/i2p.i2p/apps/i2psnark/java/build.xml:302: Warning: Could not find file /usr/home/jenkins/BUiLD/i2p.i2p/installer/resources/themes/console/classic/images/bg0.png to copy.

Total time: 3 seconds
ant i2psnark failed
Buildfile: /usr/home/jenkins/BUiLD/i2p.i2p/build.xml
#2442 invalid Option to disable SSU Peer Test zzz zab
Description

While working with Arctic I discovered that his firewall configuration actually changes the source port in outgoing datagrams to a random value. This breaks the current Alice -> Bob -> Charlie -> Alice test because Bob forwards to Charlie the port that he sees, but that is open for responses only from Bob.

As a result after running the test the router decides that it's firewalled even though the appropriate ports are forwarded correctly and inbound unsolicited SSU sessions get established just fine.

As it would be too much work to redesign the peer test to cater to this rare type of firewall, I suggest we just add an option to disable the test altogether.

#2437 fixed issues on translated webpage: Unexpected section title or transition slumlord echelon
Description
2221] /opt/i2p.website/i2p.www/i2p2www/blog	21	(WARNING/2) Bullet list ends without a blank line; unexpected unindent.			
2221] /opt/i2p.website/i2p.www/i2p2www/blog	36	(WARNING/2) Title underline too short.			
2221]					
2221] Nice-to-have	Penggunaan kembali kode pemograman				
2221] ------------------------					
2221] /opt/i2p.website/i2p.www/i2p2www/blog	36	(WARNING/2) Title underline too short.			
2221]					
2221] Nice-to-have	Penggunaan kembali kode pemograman				
2221] ------------------------					
2221] /opt/i2p.website/i2p.www/i2p2www/blog	54	(WARNING/2) Title underline too short.			
2221]					
2221] Prioritas	Kolaborasi dengan clearnet				
2221] --------------------------------					
2221] /opt/i2p.website/i2p.www/i2p2www/blog	54	(WARNING/2) Title underline too short.			
2221]					
2221] Prioritas	Kolaborasi dengan clearnet				
2221] --------------------------------					
2221] /opt/i2p.website/i2p.www/i2p2www/blog	84	(WARNING/2) Title underline too short.			
2221]					
2221] Prioritas	Penerapan Plugin di aplikasi-aplikasi sekarang				
2221] ---------------------------------------					
2221] /opt/i2p.website/i2p.www/i2p2www/blog	84	(WARNING/2) Title underline too short.			
2221]					
2221] Prioritas	Penerapan Plugin di aplikasi-aplikasi sekarang				
2221] ---------------------------------------					
2221] /opt/i2p.website/i2p.www/i2p2www/blog	98	(WARNING/2) Title underline too short.			
2221]					
2221] Nice-to-have	Pengembangan aplikasi				
2221] ------------------------------					
2221] /opt/i2p.website/i2p.www/i2p2www/blog	98	(WARNING/2) Title underline too short.			
2221]					
2221] Nice-to-have	Pengembangan aplikasi				
2221] ------------------------------					
2221] /opt/i2p.website/i2p.www/i2p2www/blog	115	(WARNING/2) Title underline too short.			
2221]					
2221] Priority	Dukungan pengguna				
2221] ----------------------					
2221] /opt/i2p.website/i2p.www/i2p2www/blog	115	(WARNING/2) Title underline too short.			
2221]					
2221] Priority	Dukungan pengguna				
2221] ----------------------					
2221] /opt/i2p.website/i2p.www/i2p2www/blog	120	(WARNING/2) Title underline too short.			
2221]					
2221] Kami akan sangat senang dengan bantuan Anda!					
2221] --------------------					
2221] /opt/i2p.website/i2p.www/i2p2www/blog	120	(WARNING/2) Title underline too short.			
2221]					
2221] Kami akan sangat senang dengan bantuan Anda!					
					
21431] /opt/i2p.website/i2p.www/i2p2www/blog	23	(ERROR/3) Unknown target name	download page		
21431] /opt/i2p.website/i2p.www/i2p2www/blog	11	(ERROR/3) Unknown target name	trac ticket		
21431] /opt/i2p.website/i2p.www/i2p2www/blog	11	(ERROR/3) Unknown target name	the 0.9.8 release notes		
21431] /opt/i2p.website/i2p.www/i2p2www/blog	15	(ERROR/3) Unknown target name	download page		
21431] /opt/i2p.website/i2p.www/i2p2www/blog	26	(ERROR/3) Unknown target name	this page		
21431] /opt/i2p.website/i2p.www/i2p2www/blog	15	(ERROR/3) Unknown target name	download page		
21431] /opt/i2p.website/i2p.www/i2p2www/blog	20	(ERROR/3) Unknown target name	download page		
					
50277] \\u041f\\u043e\\u0434\\u0440\\u043e\\u0431\\u043d\\u043e\\u0441\\u0442\\u0438 \\u043e\\u0431\\u043d\\u043e\\u0432\\u043b\\u0435\\u043d\\u0438\\u044f					
50277] ==============					
50277] /opt/i2p.website/i2p.www/i2p2www/blog	57	(ERROR/3) Unknown target name	full list of fixed bugs		
5433] /opt/i2p.website/i2p.www/i2p2www/blog	11	(ERROR/3) Unknown target name	the 0.9.8 release notes		
55019] /opt/i2p.website/i2p.www/i2p2www/blog	11	(WARNING/2) Title underline too short., referer	https	//geti2p.net/ru-ru/blog/	
55019] , referer	https	//geti2p.net/ru-ru/blog/			
55019] \\u041f\\u043e\\u0434\\u0440\\u043e\\u0431\\u043d\\u043e\\u0441\\u0442\\u0438 \\u043e\\u0431\\u043d\\u043e\\u0432\\u043b\\u0435\\u043d\\u0438\\u044f, referer	https	//geti2p.net/ru-ru/blog/			
55019] ==============, referer	https	//geti2p.net/ru-ru/blog/			
55019] /opt/i2p.website/i2p.www/i2p2www/blog	57	(ERROR/3) Unknown target name	full list of fixed bugs	https	//geti2p.net/ru-ru/blog/
55019] /opt/i2p.website/i2p.www/i2p2www/blog	11	(WARNING/2) Title underline too short., referer	https	//geti2p.net/ru-ru/blog/	
55019] , referer	https	//geti2p.net/ru-ru/blog/			
55019] \\u041f\\u043e\\u0434\\u0440\\u043e\\u0431\\u043d\\u043e\\u0441\\u0442\\u0438 \\u043e\\u0431\\u043d\\u043e\\u0432\\u043b\\u0435\\u043d\\u0438\\u044f, referer	https	//geti2p.net/ru-ru/blog/	

edited for formatting - sl

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

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

See also: TracTickets, TracReports, TracGuide, TicketQuery