https://bugs.winehq.org/show_bug.cgi?id=50815
Bug ID: 50815 Summary: Change UNCONFIRMED/NEW statuses to OPENED Product: WineHQ Bugzilla Version: 3.2.3 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: bugzilla-unknown Assignee: wine-bugs@winehq.org Reporter: gijsvrm@gmail.com CC: austinenglish@gmail.com Distribution: ---
This has been a long standing cause of user confusion, so it might be a good idea to change it.
It will inadvertently cause less spam on bugs, because users will no longer post comments to ask why a bug is still listed UNCONFIRMED instead of NEW, even though we don't currently make a distinction.
https://bugs.winehq.org/show_bug.cgi?id=50815
--- Comment #1 from Nikolay Sivov bunglehead@gmail.com --- Another option is to have initial state as NEW.
https://bugs.winehq.org/show_bug.cgi?id=50815
--- Comment #2 from Gijs Vermeulen gijsvrm@gmail.com --- (In reply to Nikolay Sivov from comment #1)
Another option is to have initial state as NEW.
This would also be fine, but I suggested the move away from NEW as it is a little ambiguous as old bugs can still be NEW after many years.
https://bugs.winehq.org/show_bug.cgi?id=50815
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
--- Comment #3 from Zebediah Figura z.figura12@gmail.com --- (In reply to Gijs Vermeulen from comment #2)
(In reply to Nikolay Sivov from comment #1)
Another option is to have initial state as NEW.
This would also be fine, but I suggested the move away from NEW as it is a little ambiguous as old bugs can still be NEW after many years.
Yes, I've seen users occasionally complain that bugs are "NEW" after years as well.
https://bugs.winehq.org/show_bug.cgi?id=50815
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net
--- Comment #4 from Anastasius Focht focht@gmx.net --- Hello folks,
I agree on 'NEW' state causing a lot of user confusion. I'm all in for making bug statuses less ambiguous.
The proposal of merging it into one status 'OPENED' will make life very hard for people who want to search for unprocessed bugs.
Why not stay with the current system and be less ambiguous on 'NEW' status? Change 'NEW' to 'CONFIRMED' and keep 'UNCONFIRMED' = initial status. This would allow to query for unprocessed issues, maintaining the status quo.
Related:
I don't think there is anything that can/should be done to reflect the actual bug triaging status. Workflows with more statuses and/or keywords (global) and/or tags (private) would make the processes even more complex, confusing and error prone.
Regards
https://bugs.winehq.org/show_bug.cgi?id=50815
--- Comment #5 from Zebediah Figura z.figura12@gmail.com --- What point is there in distinguishing between unconfirmed and confirmed?
https://bugs.winehq.org/show_bug.cgi?id=50815
--- Comment #6 from Anastasius Focht focht@gmx.net --- Hello Zeb,
--- quote --- What point is there in distinguishing between unconfirmed and confirmed? --- quote ---
'NEW' / 'CONFIRMED' = The bug was processed/reproduced by another person and/or the information from OP is trustworthy enough to assume that the bug is most likely valid. Not a hundred percent guarantee tho but still higher than 'UNCONFIRMED'.
Strictly speaking there is indeed no point because 'CONFIRMED' and 'UNCONFIRMED' statuses do not reflect whether a bug has been truly triaged (root cause identified) or not. For me this kind of information would be worth to capture in a publicly visible field (status, keyword).
For me bugs with status 'UNCONFIRMED' always had a higher priority for triaging than ten year old untriaged bugs with status 'NEW' (unless it's the random pick of the day). But that's a rather weak, subjective selection criteria.
Currently there are:
* 4178 bug reports with 'UNCONFIRMED' status * 3112 bug reports with 'NEW' status
Albeit not really related but the one thing that is becoming apparent to me with this discussion is the need to better mark/identify triaged bugs. Kind of the equivalent to bugs marked as 'STAGED'. I have few advanced search filters for that but those are not that accurate. Tags are one option but they are only visible to the user (= for my own benefit only). But that's a different discussion.
Coming back to the original topic: anything that avoids 'NEW' can be already considered an improvement, regardless if it's a direct replacement with less ambiguous name or a new simplified status.
Regards
https://bugs.winehq.org/show_bug.cgi?id=50815
Giacomo Orlandi gia_@inwind.it changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |gia_@inwind.it
--- Comment #7 from Giacomo Orlandi gia_@inwind.it --- How about: - OPENED as initial state (so nobody complains about new or unconfirmed) - CONFIRMED for the confirmed ones
That should stop most complains, still keeping the distinction.
-
WineHQ Bugzilla