Bug tracking best practices

project-management bug-tracking
Serhat Ozgel picture Serhat Ozgel · Jan 21, 2009 · Viewed 12.4k times · Source

In my company, these rules apply:

  • Only testers are allowed to create issues.
  • Developers must send e - mail a tester to have them create an issue.
  • Developers send e - mail to technical lead for having him assign an issue to themselves for issues they think they can resolve.
  • A developer cannot assign an issue to another developer (Must send e - mail to technical lead).
  • If a developer's issue is blocked by another developer's code, she must solve this problem outside of the bug tracking system.
  • Only testers are allowed to close issues which are opened by themselves.
  • All assignments must go through technical lead so he can track issues.
  • Bugs that are not directly related to user interface are not entered into the system (must be resolved externally).

What bug tracking flow are you using? Does it work well for you?

Answer

Dave picture Dave · Sep 15, 2010

alt text

Related questions

Tracking requirements across multiple projects with JIRA (or other tools)

My company has been using JIRA as a requirements tracking tool as well as a bug tracker, and it's been working pretty well while we've been working on one project at a time. We now have a scenario where we …

Read More
Is there a ticket system that also does project management?

Were looking to roll out a ticket system that also has project management capability. We're currently using Trac but we find that it's really difficult to config and also has very weak support with workflows. Ideally we want a system …

Read More
How do I close a project in Jira?

There are a few tasks still open in the backlog, but we're done with the project and I would like to close it. How do I do that?

Read More