wiki:TracQuery

Trac Ticket Queries

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.

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.

Example:

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

This is displayed as:

#42
MUD engine
#74
ATOM/RSS aggregator with GTK UI capable of handling big number of subscriptions
#1115
A Replacement for GNU Make using Haskell
#1128
Cabal + nhc98 + yhc

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:

No results

A more compact representation without the ticket summaries is also available:

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

This is displayed as:

#42, #74, #1115, #1128

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:

4

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

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#1651 invalid Bring it down up and bring a quick drink saminalatin
#1650 invalid Build your body with supplement soniagarwil
#1649 invalid Come back with chin resting on his chest soniagarwil
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> 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 164)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#1651 invalid Bring it down up and bring a quick drink saminalatin
Description

Bring it down up and bring a quick drink I'll and big finale for you heck prepared at home Blackline Elite want to stick around if not just leave it as it is go back or a PPS or call it a day be stand feed Jack night playing cover swimming pop advanced move treated as such advanced hopping in the shower jackknife take the legs 45 degrees out boom arms the site legs up in over grass of the need lift the legs up and we're going to roll down into playing positions you come up enormous now lower down holly & the umber are both hugging the died we do a Celtic women what McHugh? week 4 by get Kevin 8 return back to where you came and you have Jack night high gear up make a smooth on the high end up in Ohio lower down really work the arms and shoulders what keep free for by it 7 8 RI net two more times I want a little bath there . http://www.maletestosteronebooster.org/my-experience-with-blackline-elite/

#1650 invalid Build your body with supplement soniagarwil
Description

Attending church, I went in cardecista center and everyone said I was demonized. I cried so much. No one knows what this syndrome, so talk this nonsense. I never could have lasting emotional bonds. Then, as no drug therapy helped me more, I decided to invest in surgery. It was difficult for me in all aspects, as Alpha Shred well as being very expensive, had high risks.

To have a blood clot in the brain and die or have a seizure and die ... but I thought ... I no longer have life. My "life" came down to stay in a room all day, eating, drinking and taking drugs useless. So I talked to other patients who had the procedure done, asking about the surgery and unanimously told me so. With that gave a verdict for me, I operate! I spent a hell to try to get this surgery by SUS and nothing, my mother even wrote to Lula asking for God's sake that the state of the device as it is very expensive. Getting nothing or with SUS, nor justice, nor president, my father sold almost everything we had to buy the electrodes, cables, and the pacemaker. My situation was unsustainable, my glottis swelled so much, the vocal tics that once had to be intubated in the emergency room to be able to breathe properly. I still have a functional dysphonia caused by vocal tics.

http://www.maletestosteronebooster.org/nitro-shred-review/

#1649 invalid Come back with chin resting on his chest soniagarwil
Description

lactate levels has been accepted as the measure of the amount of energy being produced by the anaerobic system.

Alpha Shred When an athlete performs certain activity for a maximum effort, large amounts of lactate are produced. On equal terms, the more trained is the anaerobic system, higher levels of lactate produced in a maximum effort. For example, if the athlete can increase the amount of lactate produced under a maximum stress of 10 mmol / L to 13 mmol / l, whereas the same conditions, the same player will be able to complete a certain distance in a shorter time. RELATIONSHIP BETWEEN THE AEROBIC AND ANAEROBIC SYSTEMS - also considered as an important measure but less used as an indicator of athletic adaptations. The most efficient way to analyze this relationship is a gradual physical test. This is described by the ratio of lactate accumulation in the blood relative exercise intensity. http://www.maletestosteronebooster.org/nitro-shred-review/

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. 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

Last modified 22 months ago Last modified on Jul 7, 2013 12:12:11 PM