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:

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
Error in full example

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:

0

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

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#1622 duplicate xinha cms not saving changes made to the site gogo guest
#1621 invalid xinha cms not saving changes made to the site gogo guest
#1603 no action needed problem with automatic javascript code remove from textarea gogo guest
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 1470)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#1622 duplicate xinha cms not saving changes made to the site gogo guest
Description

Not sure if this will be seen by anyone, but we have 20 sites up on a server that currently use Xinha Core.

Release: 0.95 RC2 (Mo, 04 Feb 2008 18:28:42 +0100) Head: http://svn.xinha.webfactional.com/branches/0.95_stable/XinhaCore.js Revision: 955M Last Changed By: (lokal)

one of those sites is midlandcentercity.org.

Our hosting server tech support has researched to the best of their ability and have told us that the Xinha appears to be missing a module or a missing extension to php. Below is what they have told us:

This appears to be an issue with a missing extension to PHP but without further detail I cannot go much further. I can see the error_log file is getting records added to it every time someone tries to edit the file, but all I get is:

[04-Apr-2014 15:10:12] PHP Notice: Undefined variable: nav_text_list in /home/mchkids/public_html/index.php on line 122 [04-Apr-2014 15:10:12] PHP Notice: Undefined index: te in /home/mchkids/public_html/index.php on line 141

And a bunch of others with similar names.

Only the people who write the software in use here will be able to tell you specifically what's missing. Once I know that I can probably reinsert the missing extension

I'm hoping someone can help us please. Our clients need to be able to save changes to their sites. Thank you

#1621 invalid xinha cms not saving changes made to the site gogo guest
Description

Not sure if this will be seen by anyone, but we have 20 sites up on a server that currently use Xinha Core.

Release: 0.95 RC2 (Mo, 04 Feb 2008 18:28:42 +0100) Head: http://svn.xinha.webfactional.com/branches/0.95_stable/XinhaCore.js Revision: 955M Last Changed By: (lokal)

one of those sites is http://mchkids.net.

Our hosting server tech support has researched to the best of their ability and have told us that the Xinha appears to be missing a module or a missing extension to php. Below is what they have told us:

This appears to be an issue with a missing extension to PHP but without further detail I cannot go much further. I can see the error_log file is getting records added to it every time someone tries to edit the file, but all I get is:

[04-Apr-2014 15:10:12] PHP Notice: Undefined variable: nav_text_list in /home/mchkids/public_html/index.php on line 122 [04-Apr-2014 15:10:12] PHP Notice: Undefined index: te in /home/mchkids/public_html/index.php on line 141

And a bunch of others with similar names.

Only the people who write the software in use here will be able to tell you specifically what's missing. Once I know that I can probably reinsert the missing extension

I'm hoping someone can help us please. Our clients need to be able to save changes to their sites. Thank you

#1603 no action needed problem with automatic javascript code remove from textarea gogo guest
Description

Hi i use xinha for a long time and work well, i m fan of it ! ;) but i have a problem, i ll like to have the possibility to insert some javascript in the textarea , but the code is automaticly remove!?? for instance: i click on the "html source code" button, i paste this code just for test: <script type="text/javascript" id=""> </script> and after i click again on the "html source code" button to return to edit section and without do anything else i just look again the source code and my javascript code is full remove!? but if i do the test on xinha html demo, it is not remove? how is it possible that xinha don't remove the javascript code insert in the source code from the textarea? my url test page : http://www.mathieuweb.fr/test/ Thanks

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 4 years ago Last modified on 07/07/13 01:26:40