Apache OpenOffice (AOO) Bugzilla – Issue 122775
Make UNCONFIRMED default status for new Bugs
Last modified: 2017-05-20 10:45:00 UTC
I think default Status for new Bug reports should be changed from CONFIRMED to UNCONFIRMED: I did a little statistics and found that 16 of the 370 bugs reported within the last 90 days have been changed from CONFIRMED to UNCONFIRMED (see URL above). Two other ones are CONFIRMED, but have NEEDMOREINFO keyword. That seems an acceptable rate, but I suppose a ponderable number of additional ones with CONFIRMED what do not deserve that status. Novices might think "I should change as few as possible" and leave CONFIRMED, although they are not sure whether they really found a bug. We might avoid some wrong CONFIRMED with that change, what would make our queries more reliable and avoid double work.
Changing the workflow requires consensus (or lazy consensus) from the dev@openoffice.apache.org mailing list. Please suggest it there first and depending on the outcome this will be changed.
I think better safe than sorry. Only when we are in control this is good idea. For now too many unconfirmed bugs are waiting... I'm against this enhancement.
Would it be possible to offer a new option say "default status" in the "bug fields" menu. Then one could configure which status is assigned to a newly created bug. CONFIRMED or UNCONFIRMED. I am an UNCONFIRMED supporter :-)
Current configuration should not allow the typical user to open a defect in the confirmed state. Only three classes of users are able to do this: 1. Admins 2. Project committers (those with *.apache.org email addresses) 3. QA volunters (those who have asked to be be added to the qa-team list) These are the same groups that can change the status of defect reports in general. We rely on their attention to detail in many areas, including this. So we should not have random people doing this. Or are we seeing some other behavior?
I submitted the wish for a configurable confirm-preference to Bugzilla: https://bugzilla.mozilla.org/show_bug.cgi?id=915682
(In reply to Rob Weir from comment #4) > So we should not have random people doing this. Or are we seeing some other > behavior? The current bug workflow allows unconfirmed and confirmed issue submission. Bugzilla defaults new issues to confirmed status for members of the can_confirm group and unconfirmed status for random people. The enhancement request against bugzilla would allow can_confirm members to specify their preference.
(In reply to Rob Weir from comment #4) > Current configuration should not allow the typical user to open a defect in > the confirmed state. Yes, you are right, I should have checked that more carefully. Reason for my request was that I frequently found bugs with a very rare report, but but initial status CONFIRMED, so that I thought that every new user has CONFIRMED as initial Status. But a test with a sock puppet account shows that those newbies indeed have UNCONFIRMED as initial (and only possible) Status. So I currently cant see anything we could change here to make CONFIRMED more reliable.
Reset the assignee to the default "issues@openoffice.apache.org".