There are 2 items.
1. Serial numbers for each bug. It's really
a counter which would allow you to do
simple statistical stuff like the number
of issues resolved this month.....
2. A searchable text area where the admin puts
in a description of the ORIGINAL error message
and/or condition, and then in another searchable
text area, what he did to fix it.
3. Your graph (Bug Summary) is COOL!!!
Was that hard to implement ?
glbny@yahoo.com
Logged In: YES
user_id=11944
1. I don't follow how serial numbers for bugs help with the
kind of report you mention (though that kind of report is on
my mental todo list).
2. Interesting... I'll think about it
3. Thanks and nope -- check out http://www.aditus.nu/jpgraph
to find the class I used to do that.
What he actually means is that all transactions should be counted or logged somewhere. Then one could use the transaction journal for stats. But honestly, I think that such stats have nothing to say at all about quality or other metrics. They are pure eyecandy....