Available Reports
New 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} All 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.
{9} All Tickets by Component
This report shows how to color results by priority, while grouping results by component.
Last modification time, description and reporter are included as hidden fields for useful RSS export.
{10} Assigned, Active Tickets by Owner
List assigned tickets, group by ticket owner, sorted by priority.
{11} Assigned, Active Tickets by Owner (Full Description)
List tickets assigned, group by ticket owner. This report demonstrates the use of full-row display.
{12} All Tickets By Milestone (Including closed)
A more complex example to show how to make advanced reports.
{13} My Tickets
This report demonstrates the use of the automatically set $USER dynamic variable, replaced with the username of the logged in user when executed.
{14} Active Tickets, Mine first
- List all active tickets by priority.
- Show all tickets owned by the logged in user in a group first.
{15} Patches Ready for Review
This review queue lists the tickets with an open patch on Phabricator. Some patches under review do not have a ticket, but can be found with this query.
{16} Simple tickets for beginners
These tickets should be approachable for someone new to 0 A.D.
{17} Tickets in need of design decisions
These tickets need some design decisions, before they can be worked upon (further).
{19} Unanswered tickets
Tickets waiting for an answer.
{20} Pathfinding
Aimed at gathering tickets related to pathfinding, and any bugs that are linked to the new pathfinder introduced in r16751.
{21} Patches Requesting Comments
Patches where the author wants input about the implementation or other code design details.
{24} Release blockers
These issues reported in these tickets are considered obligatory to address prior to the next release.
{26} Open regressions
Tickets in this category are regressions, meaning defects in the current codebase that were not present in the same feature in the most release prior to the commit introducing the defect.
{27} Active Tickets by id
- List all active tickets by priority.
- Color each row based on priority.
