Available Reports

New Custom Query

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

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

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

Tickets Awaiting Review {40}

Tickets in the Awaiting Review milestone.

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

Theme Compatibility, Workflow Oriented {34}

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

Reports:

Tickets: All Tickets (*), Next Minor Release (*), Next Major Release (*), Future Releases (*)
Workflow: reporter-feedback => needs-patch => has-patch / needs-testing => needs-unit-tests / needs-docs => dev-feedback / needs-review => tested / commit
Special: My Tickets, My Patches, Latest, Active, Popular, Early, Blocker, Close, Punt, Multisite, Featured

Suggesting Close / Needs 2nd Opinion {17}

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:

Tickets: All Tickets (*), Next Minor Release (*), Next Major Release (*), Future Releases (*)
Workflow: reporter-feedback => needs-patch => has-patch / needs-testing => needs-unit-tests / needs-docs => dev-feedback / needs-review => tested / commit
Special: My Tickets, My Patches, Latest, Active, Popular, Early, Blocker, Close, Punt, Multisite, Featured

Popular Tickets {23}

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

Reports:

Tickets: All Tickets (*), Next Minor Release (*), Next Major Release (*), Future Releases (*)
Workflow: reporter-feedback => needs-patch => has-patch / needs-testing => needs-unit-tests / needs-docs => dev-feedback / needs-review => tested / commit
Special: My Tickets, My Patches, Latest, Active, Popular, Early, Blocker, Close, Punt, Multisite, Featured

Open Tickets I Have Patched {29}

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.

Next Minor Release, Workflow Oriented {4}

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:

Tickets: All Tickets (*), Next Minor Release (*), Next Major Release (*), Future Releases (*)
Workflow: reporter-feedback => needs-patch => has-patch / needs-testing => needs-unit-tests / needs-docs => dev-feedback / needs-review => tested / commit
Special: My Tickets, My Patches, Latest, Active, Popular, Early, Blocker, Close, Punt, Multisite, Featured

Next Minor Release {3}

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

Reports:

Tickets: All Tickets (*), Next Minor Release (*), Next Major Release (*), Future Releases (*)
Workflow: reporter-feedback => needs-patch => has-patch / needs-testing => needs-unit-tests / needs-docs => dev-feedback / needs-review => tested / commit
Special: My Tickets, My Patches, Latest, Active, Popular, Early, Blocker, Close, Punt, Multisite, Featured

Next Major Release, Workflow Oriented {6}

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:

Tickets: All Tickets (*), Next Minor Release (*), Next Major Release (*), Future Releases (*)
Workflow: reporter-feedback => needs-patch => has-patch / needs-testing => needs-unit-tests / needs-docs => dev-feedback / needs-review => tested / commit
Special: My Tickets, My Patches, Latest, Active, Popular, Early, Blocker, Close, Punt, Multisite, Featured

Next Major Release {5}

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

Reports:

Tickets: All Tickets (*), Next Minor Release (*), Next Major Release (*), Future Releases (*)
Workflow: reporter-feedback => needs-patch => has-patch / needs-testing => needs-unit-tests / needs-docs => dev-feedback / needs-review => tested / commit
Special: My Tickets, My Patches, Latest, Active, Popular, Early, Blocker, Close, Punt, Multisite, Featured

Needs User Experience / UI Feedback {35}

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:

Tickets: All Tickets (*), Next Minor Release (*), Next Major Release (*), Future Releases (*)
Workflow: reporter-feedback => needs-patch => has-patch / needs-testing => needs-unit-tests / needs-docs => dev-feedback / needs-review => tested / commit
Special: My Tickets, My Patches, Latest, Active, Popular, Early, Blocker, Close, Punt, Multisite, Featured

Needs Unit Tests / Needs Docs {12}

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:

Tickets: All Tickets (*), Next Minor Release (*), Next Major Release (*), Future Releases (*)
Workflow: reporter-feedback => needs-patch => has-patch / needs-testing => needs-unit-tests / needs-docs => dev-feedback / needs-review => tested / commit
Special: My Tickets, My Patches, Latest, Active, Popular, Early, Blocker, Close, Punt, Multisite, Featured

Needs Unit Tests {37}

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:

Tickets: All Tickets (*), Next Minor Release (*), Next Major Release (*), Future Releases (*)
Workflow: reporter-feedback => needs-patch => has-patch / needs-testing => needs-unit-tests / needs-docs => dev-feedback / needs-review => tested / commit
Special: My Tickets, My Patches, Latest, Active, Popular, Early, Blocker, Close, Punt, Multisite, Featured

Needs Reporter Feedback / Steps To Reproduce {11}

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:

Tickets: All Tickets (*), Next Minor Release (*), Next Major Release (*), Future Releases (*)
Workflow: reporter-feedback => needs-patch => has-patch / needs-testing => needs-unit-tests / needs-docs => dev-feedback / needs-review => tested / commit
Special: My Tickets, My Patches, Latest, Active, Popular, Early, Blocker, Close, Punt, Multisite, Featured

Needs RTL Work {38}

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:

Tickets: All Tickets (*), Next Minor Release (*), Next Major Release (*), Future Releases (*)
Workflow: reporter-feedback => needs-patch => has-patch / needs-testing => needs-unit-tests / needs-docs => dev-feedback / needs-review => tested / commit
Special: My Tickets, My Patches, Latest, Active, Popular, Early, Blocker, Close, Punt, Multisite, Featured

Needs Punting / Needs Wrangling {19}

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:

Tickets: All Tickets (*), Next Minor Release (*), Next Major Release (*), Future Releases (*)
Workflow: reporter-feedback => needs-patch => has-patch / needs-testing => needs-unit-tests / needs-docs => dev-feedback / needs-review => tested / commit
Special: My Tickets, My Patches, Latest, Active, Popular, Early, Blocker, Close, Punt, Multisite, Featured

Needs Patch {16}

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:

Tickets: All Tickets (*), Next Minor Release (*), Next Major Release (*), Future Releases (*)
Workflow: reporter-feedback => needs-patch => has-patch / needs-testing => needs-unit-tests / needs-docs => dev-feedback / needs-review => tested / commit
Special: My Tickets, My Patches, Latest, Active, Popular, Early, Blocker, Close, Punt, Multisite, Featured

Needs Early Attention {14}

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:

Tickets: All Tickets (*), Next Minor Release (*), Next Major Release (*), Future Releases (*)
Workflow: reporter-feedback => needs-patch => has-patch / needs-testing => needs-unit-tests / needs-docs => dev-feedback / needs-review => tested / commit
Special: My Tickets, My Patches, Latest, Active, Popular, Early, Blocker, Close, Punt, Multisite, Featured

Needs Dev / Bug Wrangler Feedback {10}

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:

Tickets: All Tickets (*), Next Minor Release (*), Next Major Release (*), Future Releases (*)
Workflow: reporter-feedback => needs-patch => has-patch / needs-testing => needs-unit-tests / needs-docs => dev-feedback / needs-review => tested / commit
Special: My Tickets, My Patches, Latest, Active, Popular, Early, Blocker, Close, Punt, Multisite, Featured

Needs Codex Work {36}

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:

Tickets: All Tickets (*), Next Minor Release (*), Next Major Release (*), Future Releases (*)
Workflow: reporter-feedback => needs-patch => has-patch / needs-testing => needs-unit-tests / needs-docs => dev-feedback / needs-review => tested / commit
Special: My Tickets, My Patches, Latest, Active, Popular, Early, Blocker, Close, Punt, Multisite, Featured

My Tickets {24}

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:

Tickets: All Tickets (*), Next Minor Release (*), Next Major Release (*), Future Releases (*)
Workflow: reporter-feedback => needs-patch => has-patch / needs-testing => needs-unit-tests / needs-docs => dev-feedback / needs-review => tested / commit
Special: My Tickets, My Patches, Latest, Active, Popular, Early, Blocker, Close, Punt, Multisite, Featured

My Patches {25}

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

Reports:

Tickets: All Tickets (*), Next Minor Release (*), Next Major Release (*), Future Releases (*)
Workflow: reporter-feedback => needs-patch => has-patch / needs-testing => needs-unit-tests / needs-docs => dev-feedback / needs-review => tested / commit
Special: My Tickets, My Patches, Latest, Active, Popular, Early, Blocker, Close, Punt, Multisite, Featured

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

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:

Tickets: All Tickets (*), Next Minor Release (*), Next Major Release (*), Future Releases (*)
Workflow: reporter-feedback => needs-patch => has-patch / needs-testing => needs-unit-tests / needs-docs => dev-feedback / needs-review => tested / commit
Special: My Tickets, My Patches, Latest, Active, Popular, Early, Blocker, Close, Punt, Multisite, Featured

Multisite Tickets, Workflow Oriented {30}

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

Reports:

Tickets: All Tickets (*), Next Minor Release (*), Next Major Release (*), Future Releases (*)
Workflow: reporter-feedback => needs-patch => has-patch / needs-testing => needs-unit-tests / needs-docs => dev-feedback / needs-review => tested / commit
Special: My Tickets, My Patches, Latest, Active, Popular, Early, Blocker, Close, Punt, Multisite, Featured

Latest Tickets {21}

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

Reports:

Tickets: All Tickets (*), Next Minor Release (*), Next Major Release (*), Future Releases (*)
Workflow: reporter-feedback => needs-patch => has-patch / needs-testing => needs-unit-tests / needs-docs => dev-feedback / needs-review => tested / commit
Special: My Tickets, My Patches, Latest, Active, Popular, Early, Blocker, Close, Punt, Multisite, Featured

Has Patch / Needs Testing {13}

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:

Tickets: All Tickets (*), Next Minor Release (*), Next Major Release (*), Future Releases (*)
Workflow: reporter-feedback => needs-patch => has-patch / needs-testing => needs-unit-tests / needs-docs => dev-feedback / needs-review => tested / commit
Special: My Tickets, My Patches, Latest, Active, Popular, Early, Blocker, Close, Punt, Multisite, Featured

Google Code In {41}

Tickets that explicitly marked as being involved in Google Code In
Provide a keyword of "gci" to show up on this list

Future Releases, Workflow Oriented {8}

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:

Tickets: All Tickets (*), Next Minor Release (*), Next Major Release (*), Future Releases (*)
Workflow: reporter-feedback => needs-patch => has-patch / needs-testing => needs-unit-tests / needs-docs => dev-feedback / needs-review => tested / commit
Special: My Tickets, My Patches, Latest, Active, Popular, Early, Blocker, Close, Punt, Multisite, Featured

Future Releases {7}

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:

Tickets: All Tickets (*), Next Minor Release (*), Next Major Release (*), Future Releases (*)
Workflow: reporter-feedback => needs-patch => has-patch / needs-testing => needs-unit-tests / needs-docs => dev-feedback / needs-review => tested / commit
Special: My Tickets, My Patches, Latest, Active, Popular, Early, Blocker, Close, Punt, Multisite, Featured

Featured Bugs {28}

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:

Tickets: All Tickets (*), Next Minor Release (*), Next Major Release (*), Future Releases (*)
Workflow: reporter-feedback => needs-patch => has-patch / needs-testing => needs-unit-tests / needs-docs => dev-feedback / needs-review => tested / commit
Special: My Tickets, My Patches, Latest, Active, Popular, Early, Blocker, Close, Punt, Multisite, Featured

Enhancements and Feature Requests, Next Major Release {32}

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:

Tickets: All Tickets (*), Next Minor Release (*), Next Major Release (*), Future Releases (*)
Workflow: reporter-feedback => needs-patch => has-patch / needs-testing => needs-unit-tests / needs-docs => dev-feedback / needs-review => tested / commit
Special: My Tickets, My Patches, Latest, Active, Popular, Early, Blocker, Close, Punt, Multisite, Featured

Commit Messages, Current Release {33}

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.

Commit Candidates by Wranglers {27}

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.