Version 32 (modified by 13 years ago) ( diff ) | ,
---|
This page documents the 1.4 (latest stable) release. Documentation for other releases can be found here.
Note: this page documents the 0.12 version of Trac, see 0.11/TracQuery if you need the previous version
Trac Ticket Queries
Table of Contents
Languages:
- Deutsch
- English
In addition to reports, Trac provides support for custom ticket queries, used to display lists of tickets meeting a specified set of 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 and no name/email 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 of 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.
Once you've edited your filters click the Update button to refresh your results.
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.
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:
Using the [[TicketQuery]]
Macro
The TicketQuery macro lets you display lists of tickets matching certain criteria anywhere you can use WikiFormatting.
Example:
[[TicketQuery(version=0.6|0.7&resolution=duplicate)]]
This is displayed as:
- #181
- Wiki preview injects new lines
- #204
- request for colour legend (or something similar) for ticket groups in reports
- #226
- Ticket Dependencies
- #239
- Link to diff of specifik wiki change instead of the page itself
- #351
- All ticket modifications should be tracked in timeline
- #413
- Installing on Windows, drive other than C:
- #450
- Diffviewer should try to convert the text into utf-8.
- #475
- merging of similar tickets
- #519
- Python process sometimes hangs on Windows Server 2003
- #529
- IE 5-6 over HTTPS broken downloads
Just like the query: wiki links, the parameter of this macro expects a query string formatted according to the rules of the simple ticket query language.
A more compact representation without the ticket summaries is also available:
[[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]]
This is displayed as:
Finally, if you wish to receive only the number of defects that match the query, use the count
parameter.
[[TicketQuery(version=0.6|0.7&resolution=duplicate, count)]]
This is displayed as:
The following expression:
[[TicketQuery(id=1)]]
Is displayed as:
- #1
- Add a new project summary module.
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 by placing pipes (|
) between the columns like below:
[[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter)]]
This is displayed as:
Results (1 - 3 of 11276)
Full rows
In table format you can also have full rows by using rows≤field> like below:
[[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 11276)
Ticket | Resolution | Summary | Owner | Reporter | |||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
#13754 | fixed | Blame view doesn't work when the repository name has meta characters | |||||||||||||||||||||||||||||
Description |
The following error is logged after clicking revision number in rev column of blame view for the repository name has meta characters. 2024-05-26 10:57:06,360 Trac[main] WARNING: [127.0.0.1] HTTPInternalServerError: 500 Trac Error (Repository 'svn&amp;repos' not found), <RequestWithSession "GET '/changeset/3/svn&amp;repos?annotate=%2Fnormal.txt'">, referrer 'http://127.0.0.1:3000/tracenv/browser/svn%26amp%3Brepos/normal.txt?annotate=blame'
We should use
|
||||||||||||||||||||||||||||||
#13751 | fixed | Logging non-ascii text to file failed on running with mod_wsgi | |||||||||||||||||||||||||||||
Description |
apache2.services typically run with C locale. The log output to the file with mod_wsgi using ascii encoding, so logging non-ascii string will fail. The following is logged in error.log of apache2 when the error occurs: [Tue May 21 08:38:27.959113 2024] [wsgi:error] [pid 1908845:tid 140306708121344] [remote 127.0.0.1:61286] --- Logging error --- [Tue May 21 08:38:27.970746 2024] [wsgi:error] [pid 1908845:tid 140306708121344] [remote 127.0.0.1:61286] Traceback (most recent call last): [Tue May 21 08:38:27.970949 2024] [wsgi:error] [pid 1908845:tid 140306708121344] [remote 127.0.0.1:61286] File "/home/jun66j5/venv/trac/1.6/lib/python3.11/site-packages/trac/web/main.py", line 609, in dispatch_request [Tue May 21 08:38:27.970961 2024] [wsgi:error] [pid 1908845:tid 140306708121344] [remote 127.0.0.1:61286] dispatcher.dispatch(req) [Tue May 21 08:38:27.970970 2024] [wsgi:error] [pid 1908845:tid 140306708121344] [remote 127.0.0.1:61286] File "/home/jun66j5/venv/trac/1.6/lib/python3.11/site-packages/trac/web/main.py", line 301, in dispatch [Tue May 21 08:38:27.970974 2024] [wsgi:error] [pid 1908845:tid 140306708121344] [remote 127.0.0.1:61286] raise e [Tue May 21 08:38:27.970981 2024] [wsgi:error] [pid 1908845:tid 140306708121344] [remote 127.0.0.1:61286] File "/home/jun66j5/venv/trac/1.6/lib/python3.11/site-packages/trac/web/main.py", line 247, in dispatch [Tue May 21 08:38:27.970985 2024] [wsgi:error] [pid 1908845:tid 140306708121344] [remote 127.0.0.1:61286] resp = chosen_handler.process_request(req) [Tue May 21 08:38:27.970995 2024] [wsgi:error] [pid 1908845:tid 140306708121344] [remote 127.0.0.1:61286] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [Tue May 21 08:38:27.971006 2024] [wsgi:error] [pid 1908845:tid 140306708121344] [remote 127.0.0.1:61286] File "/home/jun66j5/venv/trac/1.6/lib/python3.11/site-packages/trac/admin/web_ui.py", line 83, in process_request [Tue May 21 08:38:27.971012 2024] [wsgi:error] [pid 1908845:tid 140306708121344] [remote 127.0.0.1:61286] raise HTTPNotFound(_("No administration panels available")) [Tue May 21 08:38:27.971042 2024] [wsgi:error] [pid 1908845:tid 140306708121344] [remote 127.0.0.1:61286] abc.HTTPNotFound: 404 Not Found (Keine Administrations-Seiten verf\xc3\xbcgbar) [Tue May 21 08:38:27.971095 2024] [wsgi:error] [pid 1908845:tid 140306708121344] [remote 127.0.0.1:61286] [Tue May 21 08:38:27.971103 2024] [wsgi:error] [pid 1908845:tid 140306708121344] [remote 127.0.0.1:61286] During handling of the above exception, another exception occurred: [Tue May 21 08:38:27.971108 2024] [wsgi:error] [pid 1908845:tid 140306708121344] [remote 127.0.0.1:61286] [Tue May 21 08:38:27.971120 2024] [wsgi:error] [pid 1908845:tid 140306708121344] [remote 127.0.0.1:61286] Traceback (most recent call last): [Tue May 21 08:38:27.971175 2024] [wsgi:error] [pid 1908845:tid 140306708121344] [remote 127.0.0.1:61286] File "/usr/lib/python3.11/logging/__init__.py", line 1113, in emit [Tue May 21 08:38:27.971184 2024] [wsgi:error] [pid 1908845:tid 140306708121344] [remote 127.0.0.1:61286] stream.write(msg + self.terminator) [Tue May 21 08:38:27.971197 2024] [wsgi:error] [pid 1908845:tid 140306708121344] [remote 127.0.0.1:61286] UnicodeEncodeError: 'ascii' codec can't encode character '\\xfc' in position 123: ordinal not in range(128) [Tue May 21 08:38:27.971211 2024] [wsgi:error] [pid 1908845:tid 140306708121344] [remote 127.0.0.1:61286] Call stack: [Tue May 21 08:38:27.971286 2024] [wsgi:error] [pid 1908845:tid 140306708121344] [remote 127.0.0.1:61286] File "/home/jun66j5/venv/trac/1.6/lib/python3.11/site-packages/trac/web/main.py", line 613, in dispatch_request [Tue May 21 08:38:27.971294 2024] [wsgi:error] [pid 1908845:tid 140306708121344] [remote 127.0.0.1:61286] _send_user_error(req, env, e) [Tue May 21 08:38:27.971301 2024] [wsgi:error] [pid 1908845:tid 140306708121344] [remote 127.0.0.1:61286] File "/home/jun66j5/venv/trac/1.6/lib/python3.11/site-packages/trac/web/main.py", line 674, in _send_user_error [Tue May 21 08:38:27.971307 2024] [wsgi:error] [pid 1908845:tid 140306708121344] [remote 127.0.0.1:61286] env.log.warning('[%s] %s, %r, referrer %r', [Tue May 21 08:38:27.971324 2024] [wsgi:error] [pid 1908845:tid 140306708121344] [remote 127.0.0.1:61286] Message: '[%s] %s, %r, referrer %r' [Tue May 21 08:38:27.971330 2024] [wsgi:error] [pid 1908845:tid 140306708121344] [remote 127.0.0.1:61286] Arguments: ('127.0.0.1', 'HTTPNotFound: 404 Not Found (Keine Administrations-Seiten verf\xc3\xbcgbar)', <RequestWithSession "GET '/admin/x'">, None) I consider this is an issue of mod_wsgi because The file encoding is utf-8 if locale is not specified since Python 3.7 (pep:540). $ for i in python{2.7,3.{5,6,7,8,9,1{0,1,2,3}}}; do echo "$i: $(env - $i -c 'with open("/dev/null") as f: print(f.encoding)')"; done python2.7: None python3.5: ANSI_X3.4-1968 python3.6: ANSI_X3.4-1968 python3.7: UTF-8 python3.8: UTF-8 python3.9: UTF-8 python3.10: UTF-8 python3.11: utf-8 python3.12: utf-8 python3.13: utf-8
Workaround is passing
Patch is to pass
|
||||||||||||||||||||||||||||||
#13750 | worksforme | WikiFormatting inconsistent when adding numbers | |||||||||||||||||||||||||||||
Description |
When I use a CamelCase word in my tickets or wiki, e.g.
When I append a number, e.g. I would expect the behaviour to be the same, with or without numbers. See attached images. |
Query Language
query:
TracLinks and the [[TicketQuery]]
macro both use a mini “query language” for specifying query filters. Basically, the filters are separated by ampersands (&
). Each filter then 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 left out 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