Closed
Bug 31397
Opened 25 years ago
Closed 24 years ago
UNCONFIRMED state should be selected by default on query page
Categories
(Bugzilla :: Bugzilla-General, defect, P2)
Bugzilla
Bugzilla-General
Tracking
()
VERIFIED
WONTFIX
People
(Reporter: mnimbus, Assigned: justdave)
References
Details
Since the unfonfirmed state has been added, anyone searching for duplicate bugs
before entering a bug of their own has missed unconfirmed bugs unless they
specifically went back to select the unconfirmed state.
In short, Unconfirmed is the only 'Open' state that is not searched by default.
Comment 1•25 years ago
|
||
tara@tequilarista.org is the new owner of Bugzilla and Bonsai. (For details,
see my posting in netscape.public.mozilla.webtools,
news://news.mozilla.org/38F5D90D.F40E8C1A%40geocast.com .)
Assignee: terry → tara
Comment 2•24 years ago
|
||
I am missing bugs in my queries due to this problem,
raising priority. I'll dig on this tomorrow.
Severity: normal → major
Priority: P3 → P2
Comment 3•24 years ago
|
||
mcafee@netscape.com: Line 386 of defparams.pl:
"bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&order=%22Importance%22"
Make the obvious change :-)
Now you just have to get this changed on bugzilla.mozilla.org. This could be
tricky, as people like avoiding UNCONFIRMED bugs in searches ;-)
Gerv
Keywords: patch
Comment 4•24 years ago
|
||
I vote yes on this.
(can we get it soon?)
Asa
Comment 5•24 years ago
|
||
agree that this is necessary. I always go back and select unconfirmed when I'm
looking for an open bug.
Comment 6•24 years ago
|
||
Netscape/mozilla people don't think this is important,
recommend marking won't fix.
Comment 7•24 years ago
|
||
mcafee - I thought you were in favor of it also, according to your 5/30 comment
(?)
So far I've seen three people comment on it - you and Asa, two netscape'rs, who
seemed to be in favor of it, and one mozilla contributor, me, who also wants
this tiny change to be made. Plus the reporter, who obviously wants it, and
the person who voted for it.
This is necessary because new mozilla contributors don't know to search for
UNCONFIRMED bugs also when trying to confirm or find a dup of an unconfirmed
bug that they're trying to triage. Thus, they think there's no other bugs out
there, so they confirm the bug they're looking at, and now there's two of the
same bug out there.
mcafee- I know you removed yourself from cc list and prob. don't wanna hear
any more about this, but cc'ing you just for one last comment...then I won't
add ya again :)
Comment 8•24 years ago
|
||
The netscape person in charge said "no" to this request.
I think that's the wrong decision, but that's how it is
right now. I think this bug should be marked won't fix
instead of just staying open with no one working on it.
Tara has deferred this to mozilla.org, so ? I will reassign
this to leger to get some resolution here.
Assignee: tara → leger
ok...so here is the history...
1) when we went open source, many bugs came in from the net community that were
not very complete. Many newbies to writing bug and knowing how to search for
dups were writing bogus bugs and dups that took a lot of internal and external
QA cycles.
2) Engineers (external and internal) complained about this also. Lots of
"noise" in the bugs. The excelerated bug workload was not compensated with more
internal headcount to review every bug. Net community still growing, willing to
help, but needed a process to assist all.
3) Decided with Netscape internal AND mozilla folks to create an Unconfirmed
Status selection. New folks to Bugzilla would always have their bugs defaulted
to "Unconfirmed". This would give all of us (especially mozilla/netscape QA)
the radar to pick up these type of bugs. Try to reproduce or find dup first,
before hitting the engineers with a bug.
4) Engineers WANT the default query to be as accurate as possible to REAL bugs.
This solution addressed that situation.
BOTTOM LINE: NO....a default query should not pick up UNCONFIRMED. This would
defeat the whole purpose of this status setting in the first place.
Marking this Resolved/Won't Fix. If anyone still doesn't understand. Call me.
650.937.6801
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WONTFIX
Comment 11•24 years ago
|
||
I do not like to say "no" without a somewhat intelligent reason :-)
Hopefully...I was intelligent....Lord knows..I have my days...and nights :-)
Reporter | ||
Comment 12•24 years ago
|
||
First let me tell cbegle@mozilla.org that I cc'd her on this bug report because
of something I point out about the Bugzilla Helper form at the end of this
rambling.
I understand all of the arguements that mozilla/netscape engineers have against
placing UNCONFIRMED in the default search, but I still don't agree.
1) Maybe I'm wrong, but I see most Bugzilla users as reporting bugs into
bugzilla. The Netscape/Mozilla developers are in the minority (granted they
are a very important minority ;-]). Most users would benefit from seeing
UNCONFIRMED bugs in their searches, especially new users who don't know that
they should add the extra status before they search.
2) You can change your default search. Now, it could be argued either way
that the developers should change their default or that bug reporters should
change their default, but given #1 it seems to make much more sense for new
users (who don't know that they should search for Unconfirmed much less how to
make that their default search) to not have to make this change.
So, I still don't see this as defeating the purpose of the Unconfirmed status.
It doesn't bother me either way now that I've set my default to include the
Unconfirmed state. But it could still cut down on the number of duplicate bugs
being reported. At the very least, Step 2 on the Bugzilla helper page should
search for Unconfirmed bugs (it currently only searches for ASSIGNED, REOPENED,
and NEW).
Comment 13•24 years ago
|
||
This is not a netscape vs. mozilla thing. This is a project development process
which mozilla and I worked on to accommodate all. An engineer would like a QA
person to investigate a new bug from a "newbie" (which is who submits
Unconfirmed bugs) to be reproduced and the bug checked that reproducible steps
are clear and that the bug is still on latest daily build. QA also check for a
dup. All of these saves precious developer time...for all, Netscape, Sun,
Redhat, mozilla.org as a whole.
Assignee | ||
Comment 14•24 years ago
|
||
*** Bug 46508 has been marked as a duplicate of this bug. ***
Assignee | ||
Updated•23 years ago
|
Assignee: leger → justdave
Component: Bugzilla → Bugzilla-General
Product: Webtools → Bugzilla
Version: other → unspecified
Assignee | ||
Comment 15•23 years ago
|
||
moving to Bugzilla product
reassign to default owner/qa for INVALID/WONTFIX/WORKSFORME/DUPLICATE
Assignee | ||
Comment 16•23 years ago
|
||
moving to Bugzilla product
reassign to default owner/qa for INVALID/WONTFIX/WORKSFORME/DUPLICATE
Updated•20 years ago
|
OS: Windows NT → All
Hardware: PC → All
Comment 17•20 years ago
|
||
*** Bug 259379 has been marked as a duplicate of this bug. ***
Updated•12 years ago
|
QA Contact: matty_is_a_geek → default-qa
You need to log in
before you can comment on or make changes to this bug.
Description
•