QA BugHeat

From The Document Foundation Wiki
Jump to navigation Jump to search

This is just an example of what we might be able to do to identify bugs that are just dead -- then we can think about what we should do about them (adding whiteboard status might be an option). In this test case four factors are taken into consideration:

When was bug created? When was bug last modified? How many comments are on bug? Is the bug assigned to a developer?

On the summary sheet you can alter the weights of each in order to see how that affects the counts (and score). The second sheet shows the "heat meter", and the third sheet is just raw data.

Not sure if it'll be useful but there are some options that we can take data from FDO and make some cool stuff like this. Other things we can consider:

How active is the reporter? Priority/Severity (although as of now this might be useless) What component is the bug part of? What version was it reported against?