| Version 1 (modified by , 11 years ago) ( diff ) |
|---|
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
- meter_signal crashes when nfaults > 1.
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:
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 331)
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 331)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #423 | fixed | >ldd>include>host_table_dcls.incl.pl1 contains incorrect entry declarations and an unused structure | ||
| Description |
The include file >ldd>include>host_table_dcls.incl.pl1 declares five entries as returning a 40-character name, which should be a 64-character name as per host_table_mgr_ itself. host_table_mgr_$address char (40) var host_table_mgr_$name_given_address char (40) var host_table_mgr_$primary_name char (40) var host_table_mgr_$shortest_name char (40) var nit_$get_forwarding_host varying char (40) The include file also contains declarations of a host_list structure and related variables that are no longer used anywhere on Multics, and a declaration for host_table_mgr_$host_list, which doesn't exist. And it is missing declarations for five other host_table_mgr_ entries which do exist. |
|||
| #419 | invalid | telnet should accept a -port control argument to override the default telnet port | ||
| Description |
It is not possible to specify a port to connect to using the telnet protocol. We should add a -port control argument. |
|||
| #410 | fixed | bugs in message_facility_ | ||
| Description |
Bug 1a: free_msgf_mbx_ptr, line 424 The loop searching for predecessor mailbox pointers can overshoot by one and leave a freed block on the list. A mid-chain block is freed while still linked; a last-in-chain block is neither unlinked nor freed. This can cause a process hang in the message_status command. This section of code also returns error_table_$unimplemented_version when it should return error_table_$bad_subr_arg, in the case where a supplied pointer doesn’t match message_facility_’s mailbox structures (not a version mismatch). Bug 1b: get_next_msgf_mbx_ptr, line 290 message_status passes the same variable for both ptr arguments of this entry, so assigning P_next_msgf_mbx_ptr = null () destroys the input pointer before the error recovery on line 304 reads it, causing the recovery to restart at static_msgf_mbx_ptr instead of stepping past the mailbox just freed. The fix makes a copy of the input parameter as input_msgf_mbx_ptr and uses it instead. These two bugs (1a and 1b) together cause message_status -a to loop; 1a’s fix ends the loop but will still report the mailbox twice; 1b’s fix removes the duplication but by itself doesn’t terminate the loop. (To demonstrate, create and accept messages on three mailboxes, do a message_status -all, then delete the middle mailbox and do message_status -all again.) Bug 2: wakeup_processor, line 1300 The code tests whether the operation is being done on an “own” mailbox, but calls the non-own entry regardless of the test. The effect is that accept_message wakeups don’t work on a mailbox to which the user has d and o permissions but not r, when the o should govern the outcome. Bug 3: create_message_array, line 1502 Message existence bits are indexed by array positions, but these positions shift when a newly read message is inserted below existing entries. The bit array is also sized from n_messages on entry, so the shifted index can run past its end. The fix sizes it by n_elements, shifts the bits along with the entries, and widens the array deletion pass to also match. Bug 4: get_message_index, line 1454 The binary search won’t work if there are holes in the array from deleted messages; this leads to a process hang and false reports of no message. Newly allocated msg_array elements (between n_messages and n_elements) are not cleared; the fix clears them. Bug 5: print_message, line 1159 The return P_code parameter is not set when message read fails. (The pm command reports nothing when in some cases it should, when there’s a genuine error other than error_table_$no_message.) Bug 6: set_wakeup_state, line 511 The change_state variable should be initialized at the top; current code uses it before it’s initialized. Bug 7: get_msgf_mbx_ptr, line 379 A failed open leaves the new block linked, leaving a zombie entry which compounds bug 1. Bug 8: Minor issues There’s a missing return statement in an error code ^= 0 block, there are several places where substr lengths could calculate to a negative number if senders are corrupted or missing, there’s an uninitialized mbx_index variable, and an unnecessary array copy when n_messages = 0. |
|||
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
