[Libreoffice-qa] What are the requirements to set a bug to "NEW"

[Joren]

Hi Robert,

Op 10-02-13 12:07, Robert Großkopf schreef:
> Hi *,
>
> I 'm just looking for some bugs in Base. There I found bugs declared as
> "NEW", where nobody else but the report had made a comment and nothing
> is to see in the history about anybody, who has switched the report to
> "NEW".
> This bug I have set to "Needinfo". Was set to "New". Could only be set
> to "New" by the reporter.
Indeed, following the 'history' 
https://bugs.freedesktop.org/show_activity.cgi?id=60217 it's set to NEW 
when it was submitted.
> https://bugs.freedesktop.org/show_bug.cgi?id=60217
> I thought there must be someone, who could confirm the bug - not only
> the reporter. Or could we confirm our bug by ourselves?
Also correct; It's not the right workflow to 'confirm' your own bugs. 
Only (core) developers (or very experienced QA members) can set a bug to 
NEW without confirmation. Unless they are looking for a 'second 
opinion'/independent confirmation.

You did good to set the bug status to NEEDINFO because there is not 
enough info to confirm this bug. The problem with this kind of bugs is 
that: when someone set the bug status to NEW or RESOLVED WORKSFORME, we 
can't set it back to UNCONFIRMED (because the system mark it intern as 
'ever reproduced = 1').

I also see that this bug is reported directly to FDO. With our BSA, 
where most people and end users report a bug, isn't this easy/possible 
anymore to set your bug while submitting to NEW (unless they browse 
afterwards to their own bug, log in to FDO and set it as NEW).

Thanks for this cache, and you did great and correct :-).

Kind regards,
Joren