Bug tracking system


Though the Projects is initially designed as a task tracking system, it can be configured to work as a simple bug tracking system for small teams.

Here are the settings we recommend to use:

  1. Add “Bug” tag to distinguish bugs from tasks.
  2. If you prioritize your tasks, use the same priority tags for your bugs. If you don't prioritize your tasks, create two-level tags with parent “Bug” tag. You can use as many second-level tags as you like. The basic set we suggest is: “Blocker”, “Critical”,“Major”, “Minor” and “Trivial” tags, so bugs will be tagged as “Bug/Critical” or “Bug/Minor” etc. If a bug's priority is not clear, simply use “Bug” tag.
  3. Create tags to track severity. You can use as many tags as you like. The basic set we suggest is: “Crash or Data Loss”, “Major Functionality Broken”, “Minor Functionality Broken”, “Not Severe”.
  4. For large applications we suggest to group tasks by components. Possible examples are “User Account”, “Product page”, “UI design”, “Browser compatibility”, etc. Create two-level tags hierarchy with “Component” parent tag to group tasks.
  5. Use task title for bug title.
  6. Preconditions, repro steps, expected and actual results can be entered into the Notes field.
  7. Use comments and assignment to track bug's life cycle. For example when developer resolves a bug, there should be a resolution comment like “Resolved. Fixed in build 123” or “Resolved, cannot reproduce”. Bug then can be assigned to a QA engineer for regression testing.