Proposal: changing the default bug status (from 'UNCONFIRMED' to 'NEW')

[Austin English]

Howdy all,

Currently, unprivileged users have their bugs set to 'UNCONFIRMED' by
default (while privileged users have the option of
'UNCONFIRMED'/'NEW'/'ASSIGNED').

As a general rule, no one seems to care if a bug is confirmed ('NEW')
or not. This often leads to confusion for users (for example recently,
[1]), who think that because their bug is 'UNCONFIRMED', it won't get
attention.

Because this distinction is useless, I'd like to propose that we make
a few changes to Bugzilla:
* change the default status for newly submitted bugs to 'NEW' (here:
https://bugs.winehq.org/editworkflow.cgi)
* do a bulk status update of existing bugs from 'UNCONFIRMED' to 'NEW'
* disable the 'UNCONFIRMED' status (here:
https://bugs.winehq.org/editproducts.cgi?action=edit&product=Wine)

Thoughts/concerns?

[1] https://bugs.winehq.org/show_bug.cgi?id=50876

-- 
-Austin
GPG: 267B CC1F 053F 0749 (expires 2026-03-03)

[Gijs Vermeulen]

Hi!

I do agree that the 'UNCONFIRMED' & 'NEW' statuses lead to confusion. I
opened bug 50815[1] in 2021 for this reason.
No agreement was reached, however.

Having some sort of 'TRIAGED' status or something similar, does seem like a
good idea. At least to have some sort of status that reflects
that the bug has been looked at/triaged.

Kind regards,
Gijs

[1] https://bugs.winehq.org/show_bug.cgi?id=50815

Op vr 3 mei 2024 om 01:19 schreef Austin English <austinenglish(a)gmail.com>:
> Howdy all,
>
> Currently, unprivileged users have their bugs set to 'UNCONFIRMED' by
> default (while privileged users have the option of
> 'UNCONFIRMED'/'NEW'/'ASSIGNED').
>
> As a general rule, no one seems to care if a bug is confirmed ('NEW')
> or not. This often leads to confusion for users (for example recently,
> [1]), who think that because their bug is 'UNCONFIRMED', it won't get
> attention.
>
> Because this distinction is useless, I'd like to propose that we make
> a few changes to Bugzilla:
> * change the default status for newly submitted bugs to 'NEW' (here:
> https://bugs.winehq.org/editworkflow.cgi)
> * do a bulk status update of existing bugs from 'UNCONFIRMED' to 'NEW'
> * disable the 'UNCONFIRMED' status (here:
> https://bugs.winehq.org/editproducts.cgi?action=edit&product=Wine)
>
> Thoughts/concerns?
>
> [1] https://bugs.winehq.org/show_bug.cgi?id=50876
>
> --
> -Austin
> GPG: 267B CC1F 053F 0749 (expires 2026-03-03)

[Jinoh Kang]

On Fri, May 3, 2024 at 8:30 AM Gijs Vermeulen <gijsvrm(a)gmail.com> wrote:
> Hi!
>
> I do agree that the 'UNCONFIRMED' & 'NEW' statuses lead to confusion. I opened bug 50815[1] in 2021 for this reason.
> No agreement was reached, however.
>
> Having some sort of 'TRIAGED' status or something similar, does seem like a good idea. At least to have some sort of status that reflects
> that the bug has been looked at/triaged.

Maybe we can then:
1. Rename 'NEW' -> 'TRIANGED', and then
2. Rename 'UNCONFIRMED' -> 'NEW'.

-- 
Sincerely,
Jinoh Kang

[Gerald Pfeifer]

On Wed, 15 May 2024, Jinoh Kang wrote:
> > I do agree that the 'UNCONFIRMED' & 'NEW' statuses lead to confusion. I 
> > opened bug 50815[1] in 2021 for this reason. No agreement was reached, 
> > however.
> >
> > Having some sort of 'TRIAGED' status or something similar, does seem 
> > like a good idea. At least to have some sort of status that reflects 
> > that the bug has been looked at/triaged.
>
> Maybe we can then:
> 1. Rename 'NEW' -> 'TRIANGED', and then
> 2. Rename 'UNCONFIRMED' -> 'NEW'.

"Unconfirmed" is common in Bugzilla settings, so I'd leave that instead of 
it meaning something commonly associated with something else.

Gerald

Discover the latest TRB crypto price data on Toobit, including real-time market updates and comprehensive news coverage to keep you informed about the TRB market cap and trends.
https://www.toobit.com/en-US/price/TRB