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 (all)

This reports all tickets tied to 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.

{10} Tor Bundles and Installation

{12} Tor: 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.

{14} Active Torbutton Tickets

Active Torbutton Tickets, grouped by type.

{15} My Reported Tickets (based on current user)

This report lists all tickets reported, or created, by you based upon your logged in account.

{16} New Tickets

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

{17} Open Defect Tickets

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

{18} My Open Tickets (all open)

This reports all open tickets tied to the automatically set USER dynamic variable, replaced with the username of the logged in user when executed.

{19} HTTPS Everywhere Tickets

Tickets for the HTTPS Everywhere Firefox and Chrome extensions

{20} Tor Company: Active Tickets

{22} Newest 500 tickets

  • List of the newest 500 tickets

{23} Tor tickets needing review

{24} Archived Mixminion-* Tasks

{27} Open TorBirdy Tickets

{28} Open Nyx Tickets

{29} TorFlow Tickets

Tickets for the TorFlow suite, which includes the Bandwidth Authorities and SoaT.

{30} Easy Tickets

Tickets with the easy keyword. If you're new to Tor then these are a great place to start!

{31} Iteration Report: Closed Tickets

This report helps you find your recently closed tickets, sorted by last modified time, with points fields.

{32} Iteration Report: Recently Opened Tickets

This lists recently opened tickets, starting with most recent opened. This list contains some closed tickets, because we need to see those for Agile.

{33} Iteration Report: Backlog

This is your backlog: The list of open tickets, sorted by priority, that are assigned to you. Use it to select tickets for your Iteration Goals.

{34} BridgeDB Tickets

Non-closed BridgeDB tickets, with tags and last modification times, grouped by ticket priority.

{35} GetTor Tickets

Non-closed GetTor tickets

{36} Weather Tickets

Non-closed tickets for Weather

{37} Torperf product backlog

{38} Tor Browser

This report tracks tickets against Tor Browser.

{40} Tor tickets by milestone

{42} My Active Tickets (owned by me or me on the Cc list)

Show all tickets that are

  • owned by the logged in user, or
  • where the logged in user is in the Cc list.

{43} Open Stem Tickets

{44} Tickets for Tor Sysadmin Team

{45} Tickets for the Website

{46} Tor: Active Tickets

{47} Tor: Tickets needing keywords

{48} HTTPS-Everywhere Ruleset Bugs

These are bugs specific to HTTPS-Everywhere rules. Bugs appear in this report when tagged with the trac keyword 'httpse-ruleset-bug'.

{49} HTTPS Everywhere: next stable FF release

What do we need to do for the next stable Firefox release of HTTPS Everywhere?

{50} HTTPS Everywhere: next Chromium release

Tickets for the next HTTPS Everywhere chromium release

{52} Tickets for *.torproject.org services

{54} Meek open tickets

{55} BridgeDB tickets

{57} Active Tickets by Components

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

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

{58} Ooni: All non-closed tickets

{59} OPERATION ALL TICKETS

{61} Tor Core Team 2015 07 backlog

{62} TorTeam 07 2015

{64} SponsorS deiverables Y2 (029 release)

tor-chutney-usability

tickets are not part of 029 release.

https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=merge_ready&status=needs_information&status=needs_review&status=needs_revision&status=new&status=reopened&keywords=~tor-chutney-usability&col=id&col=summary&col=keywords&col=status&col=owner&col=type&col=priority&col=milestone&col=points&col=reviewer&col=sponsor&order=priority

{65} Tickets Needing Triage: Core Tor

Tickets in component "Core Tor > Tor" which may need triage, arranged by newest tickets first.

Please see https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/BugTriage for instructions on triage.

{66} Tickets Needing Triage: Unspecified Component

Please help triage these tickets by attempting to select the correct component for them!

See https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/BugTriage for more triage instructions.

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