Managing Bugs

This page is for "bug marshalls" and the development team. If you are trying to report a bug, please see ReportingBugs or GettingSupport.

If you are interested in helping with bugs, see How To Help.

Ticket reports are being moved to the ViewTickets page, as the TracReports component is being depreciated in favour of TracQuery.

Workflow

New Tickets

Tickets filed by regular users are filed with "simpleticket". This interface hides the milestone, confirmation and assign to fields, and sets them to their defaults. These fields can only be modified by someone with TICKET_ADMIN privileges.

Confirmation

After a bug has been filed, it should be reviewed. If the bug can be reproduced, it should be marked as Confirmed. If it is invalid (eg, a support request, configuration problem, filed against unsupported version) it can be closed immediately. In some cases, further information should be needed, and the Confirmation field can be used to indicate all of this.

Fix/implementation

Once a fix is created, or the feature request/patch has been implemented, the ticket can either be closed, or the confirmation field can be set to Need testing.

Confirmation field

• Unreviewed - this bug has yet to be reviewed by a developer/bug marshall.
• Need feedback - more information is needed in order to review this bug.
• Pending - this bug is in an intermediate state, possibly a behaviour covered by another bug, or it cannot be fixed until another bug is fixed. A comment should be added when moving to this state to explain why.
• Confirmed - this is a confirmed bug and can be fixed by the development team.
• Need testing - a fix has been implemented, but needs to be tested to confirm it fixes the issue.