In my company, these rules apply: <ul> <li>Only testers are allowed to create issues.</li> <li>Developers must send e - mail a tester to have them create an issue.</li> <li>Developers send e - mail to technical lead for having him assign an issue to themselves for issues they think they can resolve.</li> <li>A developer cannot assign an issue to another developer (Must send e - mail to technical lead).</li> <li>If a developer's issue is blocked by another developer's code, she must solve this problem outside of the bug tracking system.</li> <li>Only testers are allowed to close issues which are opened by themselves.</li> <li>All assignments must go through technical lead so he can track issues.</li> <li>Bugs that are not directly related to user interface are not entered into the system (must be resolved externally).</li> </ul> What bug tracking flow are you using? Does it work well for you?

Bug tracking best practices [closed]

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?

What is difference between bug tracking and issue tracking?

Bug tracking is a subset of issue tracking. Where bug tracking is only limited to reporting and management of issue within the coding, issue tracking deals with any single issue be it in the requirements/specifications, workflow, coding, design, or even post-production issue that users experience.

Which of the following will you not use for bug tracking?

Which of the following is not bug tracking tools? Explanation: Yelzilla is not bug tracking tools. 7.

How does a bugtracker work?

Typical bug tracking systems support the concept of the life cycle for a bug which is tracked through the status assigned to the bug. A bug tracking system should allow administrators to configure permissions based on status, move the bug to another status, or delete the bug.

alt text

Bug tracking best practices [closed]

Tags:

Serhat Ozgel

People also ask

1 Answers

Dave

Recent Activity

Donate For Us

Bug tracking best practices [closed]

Tags:

Serhat Ozgel

People also ask

1 Answers

Dave

Related questions

Recent Activity

Donate For Us