Bug Tracker

Learn how we track issues in our project. If you just want to visit our Bug Tracker quickly, use this link.


How to handle bugs

  1. Report new bugs as Open
  2. The project manager will assign and prioritize the bugs.
  3. The assigned developer sets the bug to Open-Accepted to indicate that she understood the bug.
    Otherwise, she sets the entry to Pending-Remind, if you don't understand it yet
  4. Declare it "Invalid", "Duplicate" or "Works for me" and set it to pending if you cannot reproduce the bug in any way
  5. If bug has been accepted and fixed, the developer should set the bug to "Fixed", but not close or set to pending.
  6. If during testing the bug is found...
    • ...to be resolved, the test team should close the bug with "Fixed" as resolution.
    • ...to still exist in the software, the test team set the bug resolution to "None" (or "Accepted") again.

Bug priorities

Has to be fixed immediately! No one leaves the building until it is fixed. :-)
Has to be fixed in the next release.
Should be fixed in the next release. If not there should be a reason why.
Varying degrees of importance.
Not prioritized yet. Project or technical manager has to do this.

How to avoid duplicate bug entries

  • If the old entry describes the exact same problem you have now, then re-open the entry.
  • If the old entry is similar and marked with a resolution suggesting no work was done ("out-of date", "invalid", etc.), then you should re-open the entry.
  • If it is similar and marked as fixed, it might be a better idea to open a new entry (and include a reference to the old one). After all, the code around the old bug changed since the old entry was added, so the problem - while similar - might be better described as caused by a different bug.
Reopening should be available to everyone listed as a project member.