wiki:TracQuery

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

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#361 invalid Couldn't making separate xcache variable cache for each php-fpm pool moo ntman
#359 invalid How to disable XCache Coverager Module moo kysil
#357 invalid PHP Startup: XCache: Unable to initialize module moo franceserv
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 311)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#361 invalid Couldn't making separate xcache variable cache for each php-fpm pool moo ntman
Description

Couldn't making separate xcache variable cache for each php-fpm pool

This is very pitiful limitation. Because I can't divide variable cache by several users for shared hosting and etc.

Also expected that for each pool I can setup own xcache password.

Example:

# cat /etc/php-fpm.d/poligon.conf [poligon] listen.owner = nginx listen.group = nginx listen = /var/run/php-fpm/poligon.sock

user = poligon group = poligon pm = dynamic pm.max_children = 50 pm.start_servers = 5 pm.min_spare_servers = 5 pm.max_spare_servers = 35 ;slowlog = /var/www/mikhail/logs/php-fpm-slow.log ;php_admin_value[error_log] = /var/www/mikhail/logs/php-fpm-error.log php_admin_flag[log_errors] = on ; Set session path to a directory owned by process user php_value[session.save_handler] = files php_value[session.save_path] = /tmp php_value[soap.wsdl_cache_dir] = /tmp ; xCache administration php_value[xcache.admin.user] = "poligon" php_value[xcache.admin.pass] = "0c51a8dd180d8a3360c88de27057c587"

#359 invalid How to disable XCache Coverager Module moo kysil
Description

Hello, I have istalled XCache php-xcache-3.2.0-1.el7.remi.5.6.x86_64

PHP 5.6.8 (cli) (built: Apr 16 2015 14:45:29) Copyright (c) 1997-2015 The PHP Group Zend Engine v2.6.0, Copyright (c) 1998-2015 Zend Technologies

with XCache v3.2.0, Copyright (c) 2005-2014, by mOo with Suhosin v0.9.37.1, Copyright (c) 2007-2014, by SektionEins? GmbH with XCache Optimizer v3.2.0, Copyright (c) 2005-2014, by mOo with XCache Cacher v3.2.0, Copyright (c) 2005-2014, by mOo with XCache Coverager v3.2.0, Copyright (c) 2005-2014, by mOo

In ini file I have this parameters: [xcache.coverager] ; enabling this feature will impact performance ; enabled only if xcache.coverager == On && xcache.coveragedump_directory == "non-empty-value"

; per request settings. can ini_set, .htaccess etc ; enable coverage data collecting and xcache_coverager_start/stop/get/clean() functions xcache.coverager = Off xcache.coverager_autostart = Off

; set in php ini file only ; make sure it's readable (open_basedir is checked) by coverage viewer script xcache.coveragedump_directory = ""

In XCache Admin I see what XCache Coverager Module is enabled : http://i.piccy.info/i9/f1766edd180beccd4b20ad3aacad8dcf/1429363548/484441/898572/xcache.png

How to fix it?

#357 invalid PHP Startup: XCache: Unable to initialize module moo franceserv
Description

Greetings,

After to have installer a second webserver with the same configuration file, i can't enable XCache on this new server and i don't understand the reason. I have the same error with 3.1 and 3.2.

This is the error when i enable the extension and i restart the server :

Gracefully shutting down php-fpm . done
Starting php-fpm [23-Mar-2015 15:10:35] NOTICE: PHP message: PHP Warning:  PHP Startup: XCache: Unable to initialize module
Module compiled with module API=20090626
PHP    compiled with module API=20100525
These options need to match
 in Unknown on line 0
 done

My compilation is this one :

/usr/local/php54/bin/phpize

Configuring for:
PHP Api Version:         20100412
Zend Module Api No:      20100525
Zend Extension Api No:   220100525

./configure --enable-xcache --with-php-config=/usr/local/php54/bin/php-config make

Build complete.
Don't forget to run 'make test'.

make test

=====================================================================
PHP         : /usr/local/php54/bin/php
CWD         : /root/fsh/install/installs/xcache/xcache-3.2.0
Extra dirs  :
VALGRIND    : Not used
=====================================================================
TIME START 2015-03-23 15:17:21
=====================================================================
FAIL xcache requires deep copying arg info [tests/xcache_deep_copy_arg_info.phpt]
FAIL xcache requires deep copying opcodes for __FILE__ and __DIR__ [tests/xcache_deep_copy_opcodes_for_const.phpt]
FAIL xcache requires deep copying static variables in shallow copy mode [tests/xcache_deep_copy_static_variables.phpt]
FAIL include absolute path [tests/xcache_include_absolute.phpt]
FAIL include relative to current working dir [tests/xcache_include_relative_cwd.phpt]
FAIL include relative to current file [tests/xcache_include_relative_file.phpt]
SKIP xcache_is_autoglobal [tests/xcache_is_autoglobal.phpt] reason: xcache extension not loaded
SKIP xcache shallow copying precondition: early binding changes constant inside opcode for PHP5.2- [tests/xcache_shallow_copy_check_early_binding.phpt] reason: only needed for PHP 5.2 or less
SKIP xcache_set/get test [tests/xcache_var.phpt] reason: xcache extension not loaded
=====================================================================
TIME END 2015-03-23 15:17:22

=====================================================================
TEST RESULT SUMMARY
---------------------------------------------------------------------
Exts skipped    :    0
Exts tested     :    1
---------------------------------------------------------------------

Number of tests :    9                 6
Tests skipped   :    3 ( 33.3%) --------
Tests warned    :    0 (  0.0%) (  0.0%)
Tests failed    :    6 ( 66.7%) (100.0%)
Expected fail   :    0 (  0.0%) (  0.0%)
Tests passed    :    0 (  0.0%) (  0.0%)
---------------------------------------------------------------------
Time taken      :    1 seconds
=====================================================================

=====================================================================
FAILED TEST SUMMARY
---------------------------------------------------------------------
xcache requires deep copying arg info [tests/xcache_deep_copy_arg_info.phpt]
xcache requires deep copying opcodes for __FILE__ and __DIR__ [tests/xcache_deep_copy_opcodes_for_const.phpt]
xcache requires deep copying static variables in shallow copy mode [tests/xcache_deep_copy_static_variables.phpt]
include absolute path [tests/xcache_include_absolute.phpt]
include relative to current working dir [tests/xcache_include_relative_cwd.phpt]
include relative to current file [tests/xcache_include_relative_file.phpt]
=====================================================================

You may have found a problem in PHP.
This report can be automatically sent to the PHP QA team at
http://qa.php.net/reports and http://news.php.net/php.qa.reports
This gives us a better understanding of PHP's behavior.
If you don't want to send the report immediately you can choose
option "s" to save it.  You can then email it to qa-reports@lists.php.net later.
Do you want to send this report now? [Yns]: n

I don't understand what is the problem because on a first server i don't have this problem.

Could you help me please ?

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

Last modified 2 months ago Last modified on 2015-05-22T07:24:45+02:00