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.
Filters
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.
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
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.
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:
No results
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:
No results
Finally if you wish to receive only the number of defects that match the query using the count parameter.
[[TicketQuery(version=0.6|0.7&resolution=duplicate, count)]]
This is displayed as:
0
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 5)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #8 | fixed | calaosd 1.1.20 : États des entrées toujours non lus au démarrage | somebody | vmeyer |
| #7 | fixed | Mauvais affichage des températures négatives. | raoul | vmeyer |
| #6 | fixed | calaosd 1.1.18 : États des entrées non lu au démarrage. | raoul | vmeyer |
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 5)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #8 | fixed | calaosd 1.1.20 : États des entrées toujours non lus au démarrage | somebody | vmeyer |
| description |
Au lancement de calaosd, seul 1 état d'entrée est lu au démarrage : Mar 3 16:25:42 calaos init: ### Starting crond Mar 3 16:25:42 calaos init: ### Starting lighttpd Mar 3 16:25:42 calaos init: ### Upload stats. Mar 3 16:25:42 calaos init: Device type is: calaos_server Mar 3 16:25:42 calaos init: Creating default Logging config (calaosd) Mar 3 16:25:42 calaos init: Set hardware clock from system clock Mar 3 16:25:42 calaos init: ### Starting calaosd Mar 3 16:25:42 calaos init: ### Loading touchscreen driver Mar 3 16:25:42 calaos init: Create xorg.conf Mar 3 16:25:42 calaos calaosd: WARN : Config::loadStateCache() could not open iostates.cache for read ! Mar 3 16:25:42 calaos calaosd: INFO : WIDigitalTriple::WIDigitalTriple(input_0): Ok Mar 3 16:25:42 calaos calaosd: INFO : IOFactory::CreateInput?(WIDigitalTriple): Ok Mar 3 16:25:42 calaos calaosd: INFO : WIDigitalTriple::WIDigitalTriple(input_1): Ok Mar 3 16:25:42 calaos calaosd: INFO : IOFactory::CreateInput?(WIDigitalTriple): Ok Mar 3 16:25:42 calaos calaosd: INFO : Internal::Internal(intern_45): Ok Mar 3 16:25:42 calaos calaosd: INFO : IOFactory::CreateInput?(InternalBool?): Ok Mar 3 16:25:42 calaos calaosd: INFO : WIDigitalBP::WIDigitalBP(input_198): Ok Mar 3 16:25:42 calaos calaosd: INFO : IOFactory::CreateInput?(WIDigitalBP): Ok Mar 3 16:25:42 calaos calaosd: INFO : WIDigitalBP::WIDigitalBP(input_199): Ok .../... Mar 3 16:25:43 calaos calaosd: INFO : ### All services started successfully, entering main loop ### Mar 3 16:25:43 calaos calaosd: INFO : WODigital(output_0): Reading initial value: false Mar 3 16:25:43 calaos calaosd: INFO : WODigital(output_1): Reading initial value: false Mar 3 16:25:43 calaos calaosd: INFO : WODigital(output_100): Reading initial value: false Mar 3 16:25:43 calaos calaosd: INFO : WODigital(output_101): Reading initial value: false Mar 3 16:25:43 calaos calaosd: INFO : WODigital(output_102): Reading initial value: false Mar 3 16:25:43 calaos calaosd: INFO : WIDigitalBP::WIDigitalBP(input_198): Reading initial state: false Mar 3 16:25:43 calaos calaosd: INFO : WODigital(output_47): Reading initial value: false Mar 3 16:25:43 calaos calaosd: INFO : WODigital(output_74): Reading initial value: true Mar 3 16:25:43 calaos calaosd: INFO : WODigital(output_105): Reading initial value: false Mar 3 16:25:43 calaos calaosd: INFO : WODigital(output_107): Reading initial value: false Mar 3 16:25:43 calaos calaosd: INFO : WODigital(output_75): Reading initial value: false Mar 3 16:25:43 calaos calaosd: INFO : WODigital(output_6): Reading initial value: false Mar 3 16:25:43 calaos calaosd: INFO : WODigital(output_5): Reading initial value: false Mar 3 16:25:43 calaos calaosd: INFO : WODigital(output_46): Reading initial value: false Mar 3 16:25:43 calaos calaosd: INFO : WODigital(output_7): Reading initial value: false Mar 3 16:25:43 calaos calaosd: INFO : WODigital(output_76): Reading initial value: false Mar 3 16:25:43 calaos calaosd: INFO : WITemp:changed(input_288 {= débarras =}) : 0 °C Mar 3 16:25:43 calaos calaosd: INFO : WODigital(output_109): Reading initial value: false Tout cela finit par l'exécution des règles au démarrage. Pour information : input_198 est : - la troisième input de io.xml - la première de type digitalBP - la première adressée sur le second wago. Rq : durant cette phase d'initialisation la lecture des variables analogiques a déjà commencée comme en atteste l'avant dernière ligne ci-dessus. Au passage avec l'"ancienne" valeur et sans sens de surcroît. |
|||
| #7 | fixed | Mauvais affichage des températures négatives. | raoul | vmeyer |
| description |
L'affichage des températures négatives relevées par une sonde pt1000 est défectueux : Feb 11 02:18:34 calaos calaosd: INFO : WITemp:changed(input_285 : 0 °C Feb 11 02:18:49 calaos calaosd: INFO : WITemp:changed(input_285 : 0.1 °C Feb 11 02:20:49 calaos calaosd: INFO : WITemp:changed(input_285 : 0 °C Feb 11 02:21:04 calaos calaosd: INFO : WITemp:changed(input_285 : 0.1 °C Feb 11 02:23:19 calaos calaosd: INFO : WITemp:changed(input_285 : 0 °C Feb 11 02:23:34 calaos calaosd: INFO : WITemp:changed(input_285 : 0.1 °C Feb 11 05:01:35 calaos calaosd: INFO : WITemp:changed(input_285 : 0 °C Feb 11 05:01:50 calaos calaosd: INFO : WITemp:changed(input_285 : 6553.5 °C Feb 11 05:02:05 calaos calaosd: INFO : WITemp:changed(input_285 : 0 °C .../... Feb 11 06:49:23 calaos calaosd: INFO : WITemp:changed(input_285 : 6553.5 °C Feb 11 06:53:08 calaos calaosd: INFO : WITemp:changed(input_285 : 6553.4 °C Feb 11 06:53:23 calaos calaosd: INFO : WITemp:changed(input_285 : 6553.5 °C Feb 11 06:53:38 calaos calaosd: INFO : WITemp:changed(input_285 : 6553.4 °C Feb 11 06:54:38 calaos calaosd: INFO : WITemp:changed(input_285 : 6553.5 °C Feb 11 06:56:23 calaos calaosd: INFO : WITemp:changed(input_285 : 6553.4 °C Feb 11 06:56:38 calaos calaosd: INFO : WITemp:changed(input_285 : 6553.5 °C |
|||
| #6 | fixed | calaosd 1.1.18 : États des entrées non lu au démarrage. | raoul | vmeyer |
| description |
L'état des entrées n'est pas lu au démarrage. Ceci est particulièrement préjudiciable pour les entrées dont l'état normal est l'état haut. Le premier passage à l'état bas n'est pas pris en compte. Par ailleurs, l'état des entrées ne peut pas être utilisé pour initialiser calaosd avec des règles s'exécutant au démarrage. Ce problème existe depuis plusieurs versions du firmware. |
|||
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.
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 |
See also: TracTickets, TracReports, TracGuide
