Version 5 (modified by trac, 6 years ago) (diff)


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.


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

Using the [[TicketQuery]] Macro

The TicketQuery macro lets you display lists of tickets matching certain criteria anywhere you can use WikiFormatting.



This is displayed as:

Spike Lowess
Center on assay
Merge on genesymbol
Error in ReplicateError
Pinbaes normalization
BasicReporter and BasicSpot
RMA plugin should check that cel files are assigned to correct cdf.
extra values pass through
Create Illumina SNP raw data type
MeV ... files are now supported (by the BASEcore) in the BASE analysis tree
MeV unable to launch appplication ... class not found exception
net.sf.basedb.illumina: Detection P-value fails if there is no negative controls in bioassayset
VirtualArray plug-in can't be installed
Exception when trying to register more than one specimen tube for a case
Change default value for protocol in "RNA quality control - create aliquots" wizard step 2
Retraction wizard
Implement the "Start page" extension

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 displays the link and description of a single ticket:


This is displayed as:

Update BasePlug-ins' firstpage

A more compact representation without the ticket summaries is:

[[TicketQuery(version=0.6|0.7&resolution=duplicate, compact)]]

This is displayed as:

#4, #5, #6, #7, #8, #9, #10, #11, #16, #18, #19, #20, #92, #125, #192, #245, #296, #347, #393, #634, #866

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


This is displayed as:

Results (1 - 3 of 1223)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#1289 fixed Exclude folders from the "Stray files" wizard Nicklas Nordborg Nicklas Nordborg
#1287 fixed LinkedCase annotation Nicklas Nordborg Nicklas Nordborg
#1286 fixed Problems with the SCAN-B report when exporting with personal information Nicklas Nordborg Nicklas Nordborg
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>:


This is displayed as:

Results (1 - 3 of 1223)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#1289 fixed Exclude folders from the "Stray files" wizard Nicklas Nordborg Nicklas Nordborg

While implementing ticket #1275 we decided to put the images from the scanned slides in the the he-hiresscans directory on the ProjectArchive server. A side-effect is that the "Stray files" wizard now detects this folder as a stray folder and want to delete it (since it is not connected to an item in BASE).

The simplest solution is probably to implement a static list of folders that should be ignored.

#1287 fixed LinkedCase annotation Nicklas Nordborg Nicklas Nordborg

It would be useful to know the relation (timewise) between the two cases for patients that have two cases. Introducing a new annotation:

  • LinkedCase: (numeric) Number of days between this case and the other case. A negative value means that the other case is before this case.

Cases that is the only one for a patient don't get a value.

We should use the "Reference date on case items" wizard to find the reference data and then also update the new annotations. Since all cases always get a reference date we don't need to handle the missing date case.

The LinkedCase annotation should be included in release exporter.

#1286 fixed Problems with the SCAN-B report when exporting with personal information Nicklas Nordborg Nicklas Nordborg

The implementation of #1285 had a side-effect on the plots. The outline on the distributions is not solid but seems to have the same transparance as the distributions. Also, the the vertical markers in the gene expression plots is not transparent.

I think this is a bug in the pdfSweep tool that we are using to remove data. Investigating the source code of that package it seems like it is not actually removing things, but instead making a copy by re-painting everything that is not in the regions marked for removal. The re-painting seems to forget to switch on/off the transparency setting in some cases.

Considering that we are only interesting in removing a few text blocks, the re-painting of everything is overkill. I think it should be possible to delve deep into the internal structure of the PDF, locate the text blocks and remove them from the existing streams.

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