|Version 9 (modified by 14 years ago) ( diff ),|
This page documents the 1.4 (latest stable) release. Documentation for other releases can be found here.
Trac Ticket Queries
Table of Contents
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.
When you first go to the query page the default filters will display all open tickets, or if you're logged in it will display open tickets assigned to you. Current filters can be removed by clicking the button to the right with the minus sign on the label. New filters are added from the pulldown list in the bottom-right corner of the filters box. 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.
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 was 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 critera 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.
While Trac does not yet allow saving a named query and somehow making it available in a navigable list, you can save references to queries in Wiki content, as described below.
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=0.8 Active tickets against 0.8]
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
[query:?status=new&status=assigned&status=reopened&group=owner Assigned tickets by owner]
Whis is displayed as:
The advantage of this approach is that you can also specify the grouping and ordering, which is not possible using the first syntax.
[[TicketQuery]] macro lets you display lists of tickets matching certain criteria anywhere you can use WikiFormatting.
This is displayed as:
- Enscript Fails on Win XP
- Possibility to create more complex workflows.
- Add ability to edit the list of "resolve" states
- Error in included report query
- Make the default text of new wiki pages configurable
- patch for wiki notifies via email
- I wish the administration of trac was more like bugzilla.
- Add an option to disable email notification on trvial ticket changes
- Allow WikiFormatting of Custom Fields in Reports
- priority/severity misunderstanding.
- Wiki spamming scripts
- Proper user authentication
- Trailing spaces in a milestone's name prevent assigned tickets to show up
- Enable trac-admin to configure "user settings" (e.g. e-mail address)
- Ticket Comment Deletion Desired
- WikiMacroObjects missing in default wiki content
- view tickets error
- "Add another attachment" button
- cc only on substantial changes
A more compact representation without the ticket summaries is also available:
This is displayed as:
query: TracLinks and the
[[TicketQuery]] macro both use a mini “query language” for specifying query filters. Basically, the filters are separate 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.
The available operators are:
|=||the field content exactly matches the 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|