Hi, Samphan Raruenrom wrote:
We submited many issues due to our work providing free web-based technical support for OOo (and some other OSSes) at www.thaiopensource.org, which require us to submit every bugs that the users found. A job that we like because it helps enhancing OOo (esp. for Thai).
Thanks.
We submit many duplicates! :-) We always do a lot of search before submitting an issue. However, searching in IssueZilla to see whether the bug has been reported is not very effective. The term that was used to report the bug may be different from the one we use to search, though we always try many terms. The reporter may report different aspect of the problem, seeing the problem from different angle, may not put keyword in the subject or the word may have many synonyms.
You can search the description, not only the subject, but admittedly that is much slower.
And I don't think you can fix the problem that people use very different wording to describe one issue.
I suspect many have encounter the very same situation. There are 9600 duplicates per all 60000+ issues. This is 16% which is very high?
It is fine if you give it a decent try. But there is only so much you can do from the outside. Handling duplicates causes relatively little work. It is still best if it isn't overloaded developers or core QA who need to do this. So it is annoying to see duplicates which can be found trivially, e.g. by searching for their summary. But where wording or perception differs, the developers are usually positioned best to find duplicates, as they already own the existing issue. This works well, unless duplicate issues end up with different owners.
I also suspect that 'duplicate' is sometimes overused by developers, in that they close as duplicate a bug that has the same cause underneath, but different symptoms. In that case it is the same bug from a developer perspective, but it is not duplicate from an end-user and QA perspective.
Is it possible to enhance the search issue feature?
It probably is possible technically. But it is unlikely to be possible within the constraints of SourceCast...
Ciao, Joerg -- Joerg Barfurth Sun Microsystems - Desktop - Hamburg >>>>>>>>>>>>>>>>>> using std::disclaimer <<<<<<<<<<<<<<<<<<<<<<< Software Engineer [EMAIL PROTECTED] OpenOffice.org Configuration http://util.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
