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

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

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

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

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.

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.

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

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

• 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

If you're looking to contribute a code fix to BuddyPress, but aren't sure where to start, these tickets should be accessible, well-described, and not too challenging to have a go at.

• 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

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

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

• 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

• 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

Tickets that are explicitly marked as needing feedback (ux-feedback or ui-feedback), or as needing UI design (needs-ui).

Sorted by milestone.

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

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