Available reports

Return to Last Query

Continue browsing through the current list of results, from the last selected report or custom query.

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} Active 3D-ATM software tickets by version

All active 3D-ATM software tickets.

Use filters fields below to also show closed bugs.

{10} Active 3D-AVC text tickets by version

All active 3D-AVC text tickets.

Use filters fields below to also show closed bugs.

{11} Active MVC+D text tickets by version

All active MVC+D text tickets.

Use filters fields below to also show closed bugs.

{12} Active 3D-AVC test model tickets by version

All active 3D-AVC test model tickets.

Use filters fields below to also show closed bugs.

{13} Incomplete support of UP-MVD coding in 3D-ATM

It seems that 3D-ATM software does not fully support Un-Paired-MVD coding specified by the MVC+D text.

Encoder cannot be configured for Up-MVD configurations when 1 depth map component is present, e.g. 2 textures and 1 depth. Encoder produces the following message and exits: "Cannot compute weighted average of depth : leaving NonlinearDepthRepresentation ON Auto-enabling DepthRepresentationInfoFlag No input sequence name was provided. Please check settings."

At the same time, encoder can be configured for coding of Up-MVD data with number of depth component more than 1, e.g 3 texture and 2 depth.

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