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} All Tickets

  • All active tickets
  • Sort by component, type, summary
  • Accepted tickets have an '*' appended to their owner's name

Reports:

{2} All Tickets, Workflow Oriented

  • All active tickets, workflow oriented
  • Sort by component, type, summary
  • Accepted tickets have an '*' appended to their owner's name

Reports:

{3} Next Minor Release

  • Active tickets slated for the next minor release
  • Sort by component, type, summary
  • Accepted tickets have an '*' appended to their owner's name

Reports:

{4} Next Minor Release, Workflow Oriented

  • Active tickets slated for the next minor release, workflow oriented
  • Sort by component, type, summary
  • Accepted tickets have an '*' appended to their owner's name

Reports:

{5} Next Major Release

  • Active tickets slated for the next major release
  • Sort by component, type, summary
  • Accepted tickets have an '*' appended to their owner's name

Reports:

{6} Next Major Release, Workflow Oriented

  • Active tickets slated for the next major release, workflow oriented
  • Sort by component, type, summary
  • Accepted tickets have an '*' appended to their owner's name

Reports:

{7} Future Releases

  • Active tickets slated for future releases or with no assigned milestone
  • Sort by component, type, summary
  • Accepted tickets have an '*' appended to their owner's name

Reports:

{8} Future Releases, Workflow Oriented

  • Active tickets slated for future releases or with no assigned milestone, workflow oriented
  • Sort by component, type, summary
  • Accepted tickets have an '*' appended to their owner's name

Reports:

{9} Commit Candidates

  • Commit Candidates, grouped by milestone
  • Sort by component, type, summary
  • Accepted tickets have an '*' appended to their owner's name

Reports:

{10} Needs Dev / Bug Wrangler Feedback

  • Tickets that need feedback from whoever reported the ticket, usually because we're failing to reproduce (keyword: reporter-feedback)
  • Sort by component, type, summary
  • Accepted tickets have an '*' appended to their owner's name
  • Yellow: Last modified more than a Month ago, Red: Last Modified more than 6 Months ago

Reports:

{11} Needs Reporter Feedback / Steps To Reproduce

  • Tickets that need feedback from whoever reported the ticket, usually because we're failing to reproduce (keyword: reporter-feedback)
  • Sort by component, type, summary
  • Accepted tickets have an '*' appended to their owner's name
  • Yellow: Last modified more than a Month ago, Red: Last Modified more than 6 Months ago

Reports:

{12} Needs Unit Tests / Needs Docs

  • Tickets that have patches but were deemed to need extra unit tests or docs before getting committed (keywords: needs-unit-tests, needs-docs)
  • Sort by component, type, summary
  • Accepted tickets have an '*' appended to their owner's name

Reports:

{13} Has Patch / Needs Testing

  • Tickets that have a patch and now need testing to make sure the patch works and doesn't introduce new bugs (keywords: has-patch, needs-testing)
  • Sort by component, type, summary
  • Accepted tickets have an '*' appended to their owner's name

Reports:

{14} Needs Early Attention

  • Tickets that are explicitly marked as needing early attention in the next major release (keyword: early)
  • Sort by component, type, summary
  • Accepted tickets have an '*' appended to their owner's name

Reports:

{16} Needs Patch

  • Tickets that lack an attachment or are explicitly marked as needing a patch (keyword: needs-patch)
  • Sort by component, type, summary
  • Accepted tickets have an '*' appended to their owner's name

Reports:

{17} Suggesting Close / Needs 2nd Opinion

  • Tickets that bug wranglers suspect are dups, and invalid/wontfix suggestions that could use a second opinion (keyword: dup, close)
  • Sort by component, type, summary
  • Accepted tickets have an '*' appended to their owner's name

Reports:

{18} Blockers For Releases

  • Potential blockers for releases
  • Sort by component, type, summary
  • Accepted tickets have an '*' appended to their owner's name

Reports:

{19} Needs Punting / Needs Wrangling

  • Tickets that have the wrong milestone and need punting or wrangling
  • Sort by component, type, summary
  • Accepted tickets have an '*' appended to their owner's name

Reports:

{21} Latest Tickets

  • All Tickets
  • Sort by created
  • Accepted tickets have an '*' appended to their owner's name
  • Highlighted tickets are still 'Awaiting Review'

Reports:

{22} Active Tcikets

  • Tickets that have been active in the past two weeks
  • Sort by modified
  • Accepted tickets have an '*' appended to their owner's name

Reports:

{23} Popular Tickets

  • Tickets that have one vote or more
  • Sort by vote, component, type, summary
  • Accepted tickets have an '*' appended to their owner's name

Reports:

{24} My Tickets

  • Tickets that you've accepted, that were assigned to you or a component you own, or that you've reported
  • Sort by component, type, summary
  • Accepted tickets have an '*' appended to their owner's name

Reports:

{25} My Patches

  • Tickets that you've contributed a patch to
  • Sort by component, type, summary
  • Accepted tickets have an '*' appended to their owner's name

Reports:

{26} bbPress.org Tickets for Importers, Themes, and the site

Grouped by component. The following components are tracked here:

  • Importer: The core importers, now in the plugins repository
  • Themes: previously bundled themes (Twenty Ten, Kakumei), now in the themes repository
  • bbPress.org: Tickets related to the workings of the bbpress.org site

{27} Commit Candidates by Wranglers

Tickets that have been reviewed by trusted Bug Wranglers and have up-to-date patches and are ready to be considered for inclusion into the bbPress core.

{28} Featured Bugs

  • Active tickets that were featured/could be featured in the bbp-devel blog's ​featured bugs posts
  • Sort by component, type, summary
  • Accepted tickets have an '*' appended to their owner's name

Reports:

{29} Open Tickets I Have Patched

This report highlights any tickets which the current user has added patches on, Yet the ticket remains open.

By default, It shows for the current user, however, you may define it via the URL as such: ​http://bbpress.trac.wordpress.org/report/29?USER=johnjamesjacoby

Colored rows are those where the ticket has been marked as needing a patch.

{30} Multisite Tickets, Workflow Oriented

  • Active tickets related to multisite functionality, workflow oriented
  • Sort by component, type, summary
  • Accepted tickets have an '*' appended to their owner's name

Reports:

{31} Multisite Tickets, Workflow Oriented, Next Major Release

  • Active tickets slated for the next major release related to multisite functionality, workflow oriented
  • Sort by component, type, summary
  • Accepted tickets have an '*' appended to their owner's name

Reports:

{32} Enhancements and Feature Requests, Next Major Release

  • Many of these tickets need to be triaged and eventually punted
  • Active enhancement and feature request tickets slated for the next major release, workflow oriented
  • Sort by component, type, summary
  • Accepted tickets have an '*' appended to their owner's name
  • Default owners in a component are shown in parentheses if the ticket status remains 'new'
  • Multisite tickets have been excluded from this report. See ​the Multisite 3.0 report.
  • Excludes tickets in the Inline Docs component

Reports:

{33} Commit Messages, Current Release

Report designed to help manage the list of contributors.

Note: If you'd like a RSS feed of the changesets a they happen, Please use ​the timeline rss feed instead.

{34} Theme Compatibility, Workflow Oriented

  • Active tickets related to theme compatibility, workflow oriented
  • Sort by component, type, summary
  • Accepted tickets have an '*' appended to their owner's name

Reports:

{35} Needs User Experience / UI Feedback

  • Tickets that lack an attachment or are explicitly marked as needing feedback (ux-feedback or ui-feedback)
  • Sort by component, type, summary
  • Accepted tickets have an '*' appended to their owner's name

Reports:

{36} Needs Codex Work

  • Tickets that explicitly marked as needing codex updates (needs-codex)
  • Remove the keyword once the Codex is updated
  • Sort by component, type, summary
  • Accepted tickets have an '*' appended to their owner's name

Reports:

{37} Needs Unit Tests

  • Tickets that explicitly marked as needing unit tests (needs-unit-tests), or tickets in the Unit Tests component
  • Remove the keyword once the unit tests are committed
  • Sort by component, type, summary
  • Accepted tickets have an '*' appended to their owner's name

Reports:

{38} Needs RTL Work

  • Tickets that explicitly marked as needing RTL work (needs-rtl or rtl-feedback), or tickets in the RTL component
  • Remove the keyword once the RTL patches are committed
  • Sort by component, type, summary
  • Accepted tickets have an '*' appended to their owner's name

Reports:

{39} Candidates for 2.1

  • Tickets that explicitly marked as candidates for 2.1
  • Provide a keyword of "2.1-early" and give it a "Future Release" to show up on this list

{40} Tickets Awaiting Review

Tickets in the Awaiting Review milestone.

Customize the query here: ​http://bbpress.trac.wordpress.org/query?milestone=Awaiting+Review.

{41} Google Code In

  • Tickets that explicitly marked as being involved in Google Code In
  • Provide a keyword of "gci" to show up on this list
Note: See TracReports for help on using and creating reports.