These reports, informal and untechnical as they were, provide potentially valuable data about problems faced by ordinary users, either actual bugs, or design flaws which caused misconfiguration ("design bugs" in effect).
How do we collect this data if Bugzilla isn't up to the job?
We collect it elsewhere, filter it and process it appropriately until it's in a shape Nokia engineers can use and then feed it to bugzilla. Here's an example.
It's not a matter of bugzilla being up to the job, but of making the best use of it.
Hm, I wonder if someone could extend mabugz' functionality beyond read-only search and add for example a wizard-style UI for submitting bugs (including searching for possible duplicates etc).
Hm, I wonder if someone could extend mabugz' functionality beyond read-only search and add for example a wizard-style UI for submitting bugs (including searching for possible duplicates etc).
In the roadmap there was more complex functions like bug reporting, voting, etc. Unfortunately I have given up Mabugz development some time ago. I would be very happy to hand over the project (and help where necessary) if someone is interested.
