Rules for a properly organized bugtracker (Mantis et al)

Question

In a specific project, we work with 10 team members.

After about a year, working on a project (and using Mantis as an error / function-tracker), bugtracker becomes more difficult to use, since no standard has been set up, which explains how to create new tasks, how to comment on tasks, etc. . This leads to many entries for the same errors, the inability to easily find errors when searching, etc.

How do you organize your bugtracker? Do you use many (sub) categories for different parts of the application (GUI, Backend, etc.), Do you use tags in the task header (for example, "[GUI] [OptionPage] Error")?

Has any of your team allowed you to introduce new tasks or is this step routed through a single "Mantis-master" (who then finds out if the new report is a duplicate or a completely new record)?

Answer 1

Always link the commit of the version control system to the problem and vice versa so that you know what commits were made, resolve the problem, and why a specific commit was made.

Answer 2

What we have done is to introduce a role for approving entries in the error tracker. This role can be shared by different people. This process should either approve, approve with a little editing, or reject the record asking for further editing or clarification.

, , () .

Answer 3

"" - ,

New: anyone can enter an error.

Confirmed: several people can upgrade it to this level. These people saw each new error for a while, and therefore they will know if this is a duplicate. Or they can pass it on to a reporter for clarification until they understand it well enough to do the job.

Confirmed: established by decision makers who basically say: "We will do this."

I really don’t remember where it was, and more importantly, I don’t know how well it works.