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 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.
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.
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. This also allows displaying the link and description of a single ticket:
[[TicketQuery(id=123)]]
This is displayed as:
- #123
- Control logging of specific object types from within Controller
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, use 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 122)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #209 | fixed | System file missing for Controller | Michael Halloran | michelpons |
| #198 | fixed | ECapeThrmPropertyNotAvailable not considered as a CAPE-OPEN error | michelpons | michelpons |
| #188 | duplicate | Three log files created for one run | Michael Halloran | michelpons |
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 122)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #209 | fixed | System file missing for Controller | Michael Halloran | michelpons |
| Description |
in a Win 8.1 Enterprise N machine, after an apparently successful installation of first the x86 version of COLTT and then of the 64-bit version, launching the 64-bit controller leads to an error message: the mfc120.dll file is indicated as missing. |
|||
| #198 | fixed | ECapeThrmPropertyNotAvailable not considered as a CAPE-OPEN error | michelpons | michelpons |
| Description |
I have a PME returning 0x8004051a to a CalcsinglePhaseProp call: PropertyPackage <WaterEthanol> : Call to CalcSinglePhaseProp
MaterialObject <1> : Call to GetPresentPhases
MaterialObject <1> : Return from GetPresentPhases - Succeeded MaterialObject <1> : Call to GetTPFraction
MaterialObject <1> : Return from GetTPFraction - Succeeded COLTT <WaterEthanol> : Windows error code returned is: 0x8004051a - not known COLTT <WaterEthanol> : No error information available, call to GetErrorInfo returned: 0x1 PropertyPackage <WaterEthanol> : Error returned from CalcSinglePhaseProp - 0x8004051a PropertyPackage <WaterEthanol> : Call to get_description PropertyPackage <WaterEthanol> : Description: pO v CALUPP failed to calculate properties that may be caused by missing parameters or other reasons, please see history file. PropertyPackage <WaterEthanol> : Return from get_description – Succeeded This is read by COLTT as a Windows error and not as a CAPE-OPEN error. It should be read as a CAPE-OPEN error. |
|||
| #188 | duplicate | Three log files created for one run | Michael Halloran | michelpons |
| Description |
Usually, whatever the number of PMCs on which logging is enabled, there is a single log file created per PME run. I have a scenario that leads to three different logs created for a single PME run. The scenario is using Aspen Hysys 8.4 CP1 with Hotfix dated February 2014. Prior to running Aspen Hysys, an XFlow file has been created using the XFlowSaver UO. The attached Stream01 file is containing the saved material stream. The point here is to save a material stream created in one PME, here COFE, and to automaticalmy load this material stream in another PME. I enable COLTT on both the TEA Thermo System and on the XFlowLodaer UO. In Aspen Hysys I start with a new case. First I define a Fluid Package as a CAPE-OPEN 1.0 Property Package which is the n-depropanizer PP from TEA Thermo System. Then I insert the XFlowLoader UO in Aspen Hysys (while in hold mode) and one Material Stream. I connect this Material Stream to the outlet Port of the XFlowLoader UO. I edit the XFlowLoader and I point to the attached Stream01 file so that it may be loaded as needed. After editing, I make the flowsheet active. Then the XFlowLoader is calculated, meaning that the contents of the Stream01 file are loaded in the UO which then sets its properties in the Aspen Hysys Material Stream. I then exit Aspen Hysys without saving the case. I obtain the three attached logs. There should be only one log file. |
|||
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