Available Reports

New Custom Query

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

SQL reports and saved custom queries Sort by: Identifier Title

Accepted, Active Tickets by Owner {4}

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

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

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

Active Tickets (defects) {1}

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

Active Tickets by Milestone {3}

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.

Active Tickets by Version {2}

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.

Active Tickets, Mine first {8}

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

All Tickets By Milestone (Including closed) {6}

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

All open tickets by descending modification date {13}

All open tickets last commented on by someone other than you {14}

Feature Requests {11}

List all Feature Requests

My Tickets {7}

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

Open SCI tickets by last modified date {10}

Open SCI32 tickets by last modified date {12}

Open SCI32 tickets by priority, grouped by type {15}

Open tickets by component {9}

Release blockers {16}

This list of blockers was generated by searching for crashes, hangs, and known memory bugs across all open bug reports.

If you are a developer, please take ownership of any bugs that you are graciously willing to at least review. You may ignore any bugs that already have an owner listed.

Not all bugs here must to be fixed in order to be removed from the release blocking list. Some of these bugs may require larger architectural changes which are not feasible, so they just need reviewing by someone that can take some step toward resolving the bug, whether that is debugging to find the root cause, coming up with a concrete plan, or just re-verifying that the bug actually exists. If you own a bug that can’t be fixed by the next release just reset its priority to High.

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