| Version 4 (modified by , 12 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
- Chart fullscreen function is broken.
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 15158)
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 15158)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #19259 | fixed | [kernel] PANIC: _mutex_lock(): double lock of 0xffffffff8c072db0 by thread 49 | ||
| Description |
Updated from hrev58330 to hrev58344 in VMware Workstation 17.6.1 and now it crashes on boot: KERN: PANIC: _mutex_lock(): double lock of 0xffffffff8c072db0 by thread 49 KERN: Welcome to Kernel Debugging Land... KERN: Thread 49 "mount_server" running on CPU 0 KERN: stack trace for thread 49 "mount_server" KERN: kernel stack: 0xffffffff81a41000 to 0xffffffff81a46000 KERN: user stack: 0x00007f799e840000 to 0x00007f799f840000 KERN: frame caller <image>:function + offset KERN: 0 ffffffff81a45490 (+ 32) ffffffff801526b0 <kernel_x86_64> arch_debug_call_with_fault_handler + 0x1a KERN: 1 ffffffff81a454e0 (+ 80) ffffffff800b8388 <kernel_x86_64> debug_call_with_fault_handler + 0x78 KERN: 2 ffffffff81a45540 (+ 96) ffffffff800b9a74 <kernel_x86_64> kernel_debugger_loop(char const*, char const*, __va_list_tag*, int) + 0xf4 KERN: 3 ffffffff81a45590 (+ 80) ffffffff800b9e0e <kernel_x86_64> kernel_debugger_internal(char const*, char const*, __va_list_tag*, int) + 0x6e KERN: 4 ffffffff81a45680 (+ 240) ffffffff800ba1a7 <kernel_x86_64> panic + 0xb7 KERN: 5 ffffffff81a456d0 (+ 80) ffffffff8009d671 <kernel_x86_64> _mutex_lock(mutex*, void*) + 0x281 KERN: 6 ffffffff81a45730 (+ 96) ffffffff8004f5a2 <kernel_x86_64> _GLOBAL__N_1::BlockPrefetcher::IterativeIOFinishedHook(void*, IORequest*, int, bool, unsigned long) + 0x42 KERN: 7 ffffffff81a45770 (+ 64) ffffffff800ff792 <kernel_x86_64> do_iterative_fd_io_finish(void*, IORequest*, int, bool, unsigned long) + 0x32 KERN: 8 ffffffff81a457f0 (+ 128) ffffffff800dcc30 <kernel_x86_64> IORequest::NotifyFinished() + 0x150 KERN: 9 ffffffff81a45870 (+ 128) ffffffff800dcc50 <kernel_x86_64> IORequest::NotifyFinished() + 0x170 KERN: 10 ffffffff81a458d0 (+ 96) ffffffff800dae80 <kernel_x86_64> IOCache::ScheduleRequest(IORequest*) + 0xd0 KERN: 11 ffffffff81a45920 (+ 80) ffffffff801134a6 <kernel_x86_64> vfs_vnode_io + 0x36 KERN: 12 ffffffff81a45a10 (+ 240) ffffffff8011375a <kernel_x86_64> do_iterative_fd_io_iterate(void*, IORequest*, bool*) + 0x25a KERN: 13 ffffffff81a45a70 (+ 96) ffffffff80113b46 <kernel_x86_64> do_iterative_fd_io + 0xe6 KERN: 14 ffffffff81a45ae0 (+ 112) ffffffff80056fda <kernel_x86_64> block_cache_prefetch + 0x5ba KERN: 15 ffffffff81a45bb0 (+ 208) ffffffff81f725bb <fat> dosfs_mount(fs_volume*, char const*, unsigned int, char const*, long*) + 0xeab KERN: 16 ffffffff81a45d90 (+ 480) ffffffff80109025 <kernel_x86_64> fs_mount(char*, char const*, char const*, unsigned int, char const*, bool) + 0x805 KERN: 17 ffffffff81a45f20 (+ 400) ffffffff8011011e <kernel_x86_64> _user_mount + 0x22e KERN: 18 ffffffff81a45f30 (+ 16) ffffffff8015428f <kernel_x86_64> x86_64_syscall_entry + 0xfb KERN: user iframe at 0xffffffff81a45f30 (end = 0xffffffff81a45ff8) KERN: rax 0x69 rbx 0x7f799f83eea0 rcx 0xe762c59bac KERN: rdx 0x0 rsi 0x1060355197d0 rdi 0x1060354c7780 KERN: rbp 0x7f799f83ef00 r8 0x0 r9 0x0 KERN: r10 0x1 r11 0x206 r12 0x1060354d3e80 KERN: r13 0x1 r14 0x7f799f83ee40 r15 0x1060354c7780 KERN: rip 0xe762c59bac rsp 0x7f799f83ee08 rflags 0x206 KERN: vector: 0x63, error code: 0x0 KERN: 19 00007f799f83ef00 (+ 0) 000000e762c59bac <libroot.so> _kern_mount + 0x0c KERN: 20 00007f799f83ef20 (+ 32) 0000008e78b70e85 <_APP_> MountArchivedVisitor::~MountArchivedVisitor() + 0x65 KERN: 21 00007f799f83f0a0 (+ 384) 0000008e78b721b4 <_APP_> AutoMounter::_MountVolumes(mount_mode, mount_mode, bool, int) + 0x124 KERN: 22 00007f799f83f120 (+ 128) 0000008e78b72234 <_APP_> AutoMounter::ReadyToRun() + 0x34 KERN: 23 00007f799f83f370 (+ 592) 00000052ced5b397 <libbe.so> BApplication::DispatchMessage(BMessage*, BHandler*) + 0x467 KERN: 24 00007f799f83f3c0 (+ 80) 00000052ced631d4 <libbe.so> BLooper::task_looper() + 0x294 KERN: 25 00007f799f83f3e0 (+ 32) 00000052ced58151 <libbe.so> BApplication::Run() + 0x21 KERN: 26 00007f799f83f660 (+ 640) 0000008e78b70c45 <_APP_> main + 0x25 KERN: 27 00007f799f83f690 (+ 48) 0000008e78b70d8e <_APP_> _start + 0x3e KERN: 28 00007f799f83f6c0 (+ 48) 00000103f03f6e95 </boot/system/runtime_loader@0x00000103f03e7000> <unknown> + 0xfe95 KERN: 29 0000000000000000 (+ 0) 00007fdf85ee7258 <commpage> commpage_thread_exit + 0x00 |
|||
| #19258 | invalid | Web (epiphany) and Nightely crashes when copy/paste text | ||
| Description |
When you try to copy/paste text from the serch bar, both apps crashes. Steps to repro the issue:
Note: this happens both on web app and nightly |
|||
| #19257 | fixed | HaikuDepot - search did not include package description (regression) | ||
| Description |
Since a few nightlies, looks like the search function in HaikuDepot did not include the package description. For example, if I search for "emulator", it only shows the package that include "emulator" as part of the package name,but ignores the ones that include the search keyword as part of the package description. Please, check the attached pictures, where I compare the search function within HaikuDepot, with the ones done from the HaikuDepot web interface. Haiku hrev58305 (32 bit version) |
|||
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
