wiki:TracQuery

Trac Ticket Queries

In addition to reports, Trac provides support for custom ticket queries, which can be used to display tickets that meet specified 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 in and no name/email is 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 on 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.

After you have 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 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.

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:

Active tickets against 1.0

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:

Assigned tickets by owner

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 in by placing pipes (|) between the columns:

[[TicketQuery(max=3,status=closed,order=id,desc=1,format=table,col=resolution|summary|owner|reporter)]]

This is displayed as:

Results (1 - 3 of 29)

1 2 3 4 5 6 7 8 9 10
Ticket Resolution Summary Owner Reporter
#35 fixed OS X/wx29: building basis functions progress indicator leaks memory flip flip
#34 fixed Ubuntu: IndexError when re-running experiment somebody flip
#33 fixed Simulation fails to mark referenced objects public during export flip flip
1 2 3 4 5 6 7 8 9 10

Full rows

In table format you can also have full rows by using rows=<field>:

[[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 29)

1 2 3 4 5 6 7 8 9 10
Ticket Resolution Summary Owner Reporter
#35 fixed OS X/wx29: building basis functions progress indicator leaks memory flip flip
Description

When opening an existing experiment, Simulation calls build_basis_functions(). That function accepts a callback param which we use to update the status bar while the basis functions are being built.

Under OS X wxPython 2.9, we get one of these messages for each call to the callback that updates the status bar:

2012-07-19 17:32:09.885 Python[39940:6407] *** __NSAutoreleaseNoPool(): Object 0x1efc15c0 of class NSConcreteMutableData autoreleased with no pool in place - just leaking

The problem is an interaction between multiprocesssing (which build_basis_functions() uses) and some Cocoa-related memory management. I think some sort of object is being created in one thread and autoreleased in another.

I'm not sure I'd call this a wx bug since what we're doing is a bit odd. Nevetheless, it looks ugly (922 of these messages print when I open Example PRESS Ideal) and it probably is leaking memory, which isn't great.

An easy workaround is to disable status bar updates for OSX/wx2.9. There is precedent for this: there have never been status bar updates when building basis functions under Windows because I could never find callback code that would work. But disabling it under OS X would mean removing an existing feature, whereas Windows users never had the feature in the first place.

It might be a genuine bug that we should report to wx, in which case it might get fixed at some point. That might be a long wait, though.

At this point I'm not sure what to recommend.

#34 fixed Ubuntu: IndexError when re-running experiment somebody flip
Description

This problem was reported by Manoj Sammi. I was able to recreate it on Ubuntu 10.04 32 and 64-bit, but not under OS X nor Windows XP.

To recreate:

  1. Start Simulation
  2. Open a new expeirment and enter a name
  3. Choose One Pulse for the pulse seq
  4. Add alanine, aspartate, and ethanol to the experiment. (Three metabs seems important. If I just use two of these, I can't recreate the bug.)
  5. Run
  6. Click the Visualize tab
  7. Select all 3 metabs in the "Metabolites to Plot" list. (This seemingly innocuous step is important. If I skip it, I can't recreate the bug.)
  8. Return to the Simulate tab.
  9. Remove alanine and aspartate from the experiment, leaving only ethanol.
  10. Click run again. Python raises the error below.
Traceback (most recent call last):
  File "/home/me/duke/src/vespa/simulation/src/tab_visualize.py", line 142, in on_metabolites
    self.etab.plot_canvas(reset_history=True)
  File "/home/me/duke/src/vespa/simulation/src/tab_experiment.py", line 699, in plot_canvas
    b = self.basis.data[index3,index2,index1,imets,:]
IndexError: index (1) out of range (0<=index<0) in dimension 3

#33 fixed Simulation fails to mark referenced objects public during export flip flip
Description

When performing an export, Simulation correctly marks the exported object as public. However, if the object is an experiment, it might reference other objects (metabs & a pulse seq) and those objects are not marked as public although they should be.

This has been a bug since day 1. The implication is that there's metabs and pulse sequences out there that should have been marked public but weren't. As a result they may have been edited post-export which means that the definition in the user's personal database may have drifted from what was made public. This is a bug and we can't undo the effects.

We're about to fix this bug and I'm filing this ticket to mark when we discovered this bug and when we fixed it. For the record, it will be fixed in Vespa. 0.2.7 which is the same release that enabled use of real pulses in Simulation. In other words, only metabs & pulse seqs referenced by experiments were affected by this bug. Pulse seqs couldn't refer to pulse projects prior to this bug being fixed, so pulse projects have never been affected by this bug.

1 2 3 4 5 6 7 8 9 10

Query Language

query: TracLinks and the [[TicketQuery]] macro both use a mini “query language” for specifying query filters. Filters are separated by ampersands (&). Each filter 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 omitted 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, TicketQuery

Last modified 8 months ago Last modified on Sep 17, 2018, 4:56:17 PM