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 dropdown 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 dropdown 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 361)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#377 invalid noise subtraction in vHW dzollars nagelst
#376 fixed US convert fluorescence data upload gegorbet schirfv
#373 fixed mixed vbar/s discretizations in custom grid methods gegorbet demeler
1 2 3 4 5 6 7 8 9 10 11

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 361)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#377 invalid noise subtraction in vHW dzollars nagelst
Description

In the "Enhanced van Holde-Weischet" window FDS data get distorted, if one loads them up together with the noise files. Either noise files are corrupted or noise is subtracted twice?

The issue is different. You are fitting a system that is not appropriate for the models implemented in UltraScan? and fittable by 2DSA. As I described yesterday, the molecules seem to be degrading or dissociating under pressure or over time, so the material actually CHANGES as it is sedimenting. That means that in the beginning you have fast sedimenting material, in the end you have slow sedimenting material. Just look at the first 2-3 scans and you can see a big spacing between boundaries, later the spacing becomes very small. You cannot fit anything that is not at chemical equilibrium over the course of the velocity experiment with any known velocity whole boundary model. Essentially, you would have to fit every scan separately, since each scan would correspond to a different condition. The least squares fit tries to find the best "compromise" solution for this ever changing mixture and then naturally the ti noise is completely off as well (as will be the meniscus fit and the radially invariant noise). I tried to fit the data with different parameters and the problem was essentially completely insensitive to this change of parameterization, which tells me its your sample and not your machine or the software that has the problem here. I attached images of the TI noise solution to this ticket and what the FE solution + ti noise looks like and it should be immediately obvious why you get this pattern in the vHW (and any other analysis where you decide to subtract this ti noise from the data).

#376 fixed US convert fluorescence data upload gegorbet schirfv
Description

Unlike UV/Vis and Interference data uploads where the order is given as 1A 1B, 2A 2B, etc, the fluorescence data list is given as 1A 2A 3A etc and then 1B 2B 3B. Would be easier to upload as 1A 1B 2A etc

#373 fixed mixed vbar/s discretizations in custom grid methods gegorbet demeler
Description

The custom grid method should support an arbitrary number of subgrids, each subgrid with its own vbar assigned to the solutes of this subgrid. This in effect provides a means to fit multiple solutes with different vbars once their approximate s/D range is known. The 2DSA fitting method importing such a custom grid will have to assign each solute with its own specific vbar. By setting individual vbar values for each solute, the method is ultimately general and applicable to any custom grid. Errors should only be flagged if solutes have s-values that fall between -0.1 and +0.1 S (due to solvent densities similar to the 1/vbar value), or simply excluded from the model during model creation. Only grids that fall entirely within this unreasonable solute range should be flagged as an error.

1 2 3 4 5 6 7 8 9 10 11

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 19 months ago Last modified on Jul 6, 2018 5:49:47 AM