[Qt-interest] [OT] Bugs: "root cause" analysis (JIRA)?

[Oliver.Knoll at comit.ch]

Hi,

sorry for being off-topic, this is a general question about best practise in bug fixing, or rather: how to avoid it. We are using JIRA (just like Qt, to make it a bit more on-topic: http://bugreports.qt.nokia.com) for keeping track of bugs and the discussion came up how to "measure" or "track" what kind of bugs we mostly have (or the reason for the bugs), such as "occured during merging", "no test case", "no specifications", "too few coffee", "just a stupid typo" etc., in order to be able to come up with counter-measures such as "more coffee", "more test cases"...

Off course we want to keep track of this "root cause" information in a way such that it can be evaluated later on in a "systematic way" (e.g.  in the best case by simply counting, for example by using

- A specific set of "keywords" ("Merge-bug", "Typo", "Not Enough Tests", "Insufficient specification"...) you enter in JIRA somewhere

- Custom-checkboxes in JIRA (with the same meaning as the keywords)

- Excel sheet based solution

- ...

So my question: is anyone else trying to do this as well? How to you go about it?

Thank you,
  Oliver
-- 
Oliver Knoll
Dipl. Informatik-Ing. ETH
COMIT AG - ++41 79 520 95 22