Continue browsing through the current list of results, from the last selected report or custom query.

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

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

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.

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.

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.

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

Tickets that you've accepted, that were assigned to you, or that you've reported.

_{Hidden feature: /report/7?USER=$name pulls up someone else's ticket list.}

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

These tickets could use help from someone with design and/or user experience skills.

These tickets are good to start with if you're new to contributing. They're not necessarily easy -- although many are -- but they're self-contained, so that you don't need a lot of knowledge of the entire system, historical context, etc in order to make a good patch.

Tickets that you've contributed a patch to.

_{Hidden feature: /report/12?USER=$name pulls up someone else's patch list.}

Tickets that you've contributed a patch to, yet the ticket remains open.

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

_{Hidden feature: /report/13?USER=$name pulls up someone else's patch list.}