Trac Ticket Queries

Table of Contents

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 filters will display all open tickets, or if you're logged in it will display open tickets assigned to you. Current filters can be removed by clicking the button to the right with the minus sign on the label. New filters are added from the pulldown list in the bottom-right corner of the filters box. 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

While Trac does not yet allow saving a named query and somehow making it available in a navigable list, you can save references to queries in Wiki content, as described below.

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.

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 using 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 9)

Ticket Resolution Summary Owner Reporter
#17 fixed ASSERT when intersecting "criss-crossed" polygon with box barendgehrels koying
#16 fixed Run GGL through Boost Inspect Tool mloskot mloskot
#15 fixed Rename upper-case metafunction value in point_type barendgehrels mloskot

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

Ticket Resolution Summary Owner Reporter
#17 fixed ASSERT when intersecting "criss-crossed" polygon with box barendgehrels koying

Reported by koying, 2 years ago.
description

I receive an assert when doing polygon_2d by box_2d intersection in a very specific case (see image attached).

In the context of the Openstreetmap project, someone "cheated" and criss-crossed the polygon segment to avoid doing holes in the polygon. Even if the polygon construct is not valid, it should throw an exception rather than an ASSERT.

This lead to an assert with the following backtrace: 

0	msvcrt!_assert	C:\WINDOWS\system32\msvcrt.dll	0	
1	ggl::traverse<ggl::linear_ring<ggl::point_xy<double, ggl::cs::cartesian>, std::vector, std::allocator>, ggl::polygon<ggl::point_xy<double, ggl::cs::cartesian>, std::vector, std::vector, std::allocator, std::allocator>, ggl::box<ggl::point_xy<double, ggl::cs::cartesian> >, std::deque<ggl::detail::intersection::intersection_point<ggl::point_xy<double, ggl::cs::cartesian> >, std::allocator<ggl::detail::intersection::intersection_point<ggl::point_xy<double, ggl::cs::cartesian> > > >, std::back_insert_iterator<std::vector<ggl::linear_ring<ggl::point_xy<double, ggl::cs::cartesian>, std::vector, std::allocator>, std::allocator<ggl::linear_ring<ggl::point_xy<double, ggl::cs::cartesian>, std::vector, std::allocator> > > > >	traverse.hpp	372	
2	ggl::detail::intersection::intersection_polygon_box<ggl::polygon<ggl::point_xy<double, ggl::cs::cartesian>, std::vector, std::vector, std::allocator, std::allocator>, ggl::box<ggl::point_xy<double, ggl::cs::cartesian> >, std::back_insert_iterator<std::vector<ggl::polygon<ggl::point_xy<double, ggl::cs::cartesian>, std::vector, std::vector, std::allocator, std::allocator>, std::allocator<ggl::polygon<ggl::point_xy<double, ggl::cs::cartesian>, std::vector, std::vector, std::allocator, std::allocator> > > >, ggl::polygon<ggl::point_xy<double, ggl::cs::cartesian>, std::vector, std::vector, std::allocator, std::allocator> >::apply	intersection.hpp	225	
3	ggl::dispatch::intersection_reversed<ggl::box_tag, ggl::polygon_tag, ggl::polygon_tag, ggl::box<ggl::point_xy<double, ggl::cs::cartesian> >, ggl::polygon<ggl::point_xy<double, ggl::cs::cartesian>, std::vector, std::vector, std::allocator, std::allocator>, std::back_insert_iterator<std::vector<ggl::polygon<ggl::point_xy<double, ggl::cs::cartesian>, std::vector, std::vector, std::allocator, std::allocator>, std::allocator<ggl::polygon<ggl::point_xy<double, ggl::cs::cartesian>, std::vector, std::vector, std::allocator, std::allocator> > > >, ggl::polygon<ggl::point_xy<double, ggl::cs::cartesian>, std::vector, std::vector, std::allocator, std::allocator> >::apply	intersection.hpp	384	
4	ggl::intersection<ggl::polygon<ggl::point_xy<double, ggl::cs::cartesian>, std::vector, std::vector, std::allocator, std::allocator>, ggl::box<ggl::point_xy<double, ggl::cs::cartesian> >, ggl::polygon<ggl::point_xy<double, ggl::cs::cartesian>, std::vector, std::vector, std::allocator, std::allocator>, std::back_insert_iterator<std::vector<ggl::polygon<ggl::point_xy<double, ggl::cs::cartesian>, std::vector, std::vector, std::allocator, std::allocator>, std::allocator<ggl::polygon<ggl::point_xy<double, ggl::cs::cartesian>, std::vector, std::vector, std::allocator, std::allocator> > > > >	intersection.hpp	427	
5	Road::buildPath	Road.cpp	623	
6	MapView::buildFeatureSet	MapView.cpp	332	
7	MapView::paintEvent	MapView.cpp	190	
8	QWidget::event	qwidget.cpp	7687	
9	MapView::event	MapView.cpp	1172	
10	QApplicationPrivate::notify_helper	qapplication.cpp	4056	
11	QApplication::notify	qapplication.cpp	4021	
12	QCoreApplication::notifyInternal	qcoreapplication.cpp	610	
13	QCoreApplication::sendSpontaneousEvent	qcoreapplication.h	216	
14	QWidgetPrivate::drawWidget	qwidget.cpp	5079	
15	QWidgetBackingStore::sync	qbackingstore.cpp	1261	
16	QWidgetPrivate::syncBackingStore	qwidget.cpp	1603	
17	QWidget::event	qwidget.cpp	7827	
18	QMainWindow::event	qmainwindow.cpp	1399	
19	QApplicationPrivate::notify_helper	qapplication.cpp	4056	
20	QApplication::notify	qapplication.cpp	4021	
...	<More>
#16 fixed Run GGL through Boost Inspect Tool mloskot mloskot

Reported by mloskot, 3 years ago.
description

Boost provides dedicated tool to assist review of libraries requesting submission to Boost collection -  Inspect Tool.

It's a good idea to start running <em>inspect</em> against sources of GGL, so we improve quality of the library as soon as possible and to get prepared better for upcoming review(s).

Current status: Last run of Boost inspect against GGL trunk (r985, at Geodan) but without following directories:

  • 'doc' - broken links reported
  • 'projections' - does not go to upcoming review
  • 'other' - unrelated files 
mloskot@dog:~/dev/ggl/_svn/trunk$ binspect -text
Boost Inspection Report
Run Date: 22:07:41 UTC, Sunday 04 October 2009

An inspection program <http://www.boost.org/tools/inspect/index.html>
checks each file in the current Boost CVS for various problems,
generating an HTML page as output.

Totals:
  431 files scanned
  70 directories scanned (including root)
  0 problems reported

Problem counts:
  0 files missing Boost license info or having wrong reference text
  0 files missing copyright notice
  0 files with invalid line endings
  0 files that don't end with a newline
  0 bookmarks with invalid characters
  0 invalid urls
  0 broken links
  0 unlinked files
  0 file and directory name issues
  0 files with tabs
  0 files with non-ASCII chars
  0 violations of the Boost min/max guidelines
  0 usages of unnamed namespaces in headers (including .ipp files)

no errors detected

Good!

#15 fixed Rename upper-case metafunction value in point_type barendgehrels mloskot

Reported by mloskot, 3 years ago.
description

Is it too late or still possible to rename point_type<T>::R to lower-case according to the naming convention used in GGL? 

template <typename P>
struct point_type<polygon_tag, P>
{
    typedef typename ring_type<polygon_tag, P>::type R;
    typedef typename point_type<ring_tag, R>::type type;
};

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.

The available operators are:

= the field content exactly matches the 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

See also: TracTickets, TracReports, TracGuide