Hi Edwin,

Bugzilla reports are not the appropriate place to discuss such proceeding issues (what also is true for my comment before yours ...).

(a) Bugzilla help for NEEDINFO is too vague. This key word should only be used if it is obvious that the report is too vague and will not allow to reproduce the bug, or if after intensive tests by an expert there is a concrete suspect that reporter's observations depend on special circumstances what can not be investigated by tests with acceptable costs, but have to be investigated and told by reporter.

(b) Needinfo may not be used if the reviewer coincidentally does not have skills in that area. If reviewer knows an expert he should add the expert to cc with short comment. If he does not know an expert he simply should wait until someone with skills comes along, and if he thinks that the reported issue is urgent enough, reviewer can ask for help on this list.

In Issue 124683 it is obvious that it is useless to copy the autofilter function with the cells with a vertical fill. We should avoid to make fools of ourselves (QA team) asking a reporter for more explication in such simple cases.

(c) Additionally there is not an automatism for closing needinfo bugs. Especially if the needinfo is appropriate (... concrete suspect that reporter's observations depend on special circumstances ...) it might also cause lots of tests (and some lucky chance) until the roots of the problem can be found by reporter. Closing the issue report during that efforts of course would be inappropriate. This 14 days rule only is a recommendation for bugs where obviously no more relevant information can be expected.

@Edwin, @Jolatt:
"Issue 124770 - Wrong description for [email protected] mailing lis": Your comments are completely unrelated to the request for a necessary correction of the help text, what tells that the main purpose of [email protected].



CU

Rainer

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to