Available Reports

Custom Query

Compose a new ticket query by selecting filters and columns to display.

SQL reports and saved custom queries Sort by: Identifier Title

{1} Active Tickets

  • List all active tickets by priority.
  • Color each row based on priority.

{2} Active Tickets by Version

This report shows how to color results by priority, while grouping results by version.

Last modification time, description and reporter are included as hidden fields for useful RSS export.

{3} Active Tickets by Milestone

This report shows how to color results by priority, while grouping results by milestone.

Last modification time, description and reporter are included as hidden fields for useful RSS export.

{4} Accepted, Active Tickets by Owner

List accepted tickets, group by ticket owner, sorted by priority.

{5} Accepted, Active Tickets by Owner (Full Description)

List tickets accepted, group by ticket owner. This report demonstrates the use of full-row display.

{6} All Tickets By Milestone (Including closed)

A more complex example to show how to make advanced reports.

{7} My Tickets

This report demonstrates the use of the automatically set USER dynamic variable, replaced with the username of the logged in user when executed.

{8} Active Tickets, Mine first

  • List all active tickets by priority.
  • Show all tickets owned by the logged in user in a group first.

{9} iteration over (empty) transition steps

transition steps are not stored unless configured (vm.store_steps, or a 'trace' report topic), but the stepcount is updated regardless (used as progress measurement in some apps). Successive attempts to iterate over such non-stored steps causes exceptions.

As a short term fix, the step iterator should produce a clear error description. Long term, this has to be replaced with the trace storage interface (and external post-mortem trace server)

Note: See TracReports for help on using and creating reports.