Let's get rid of UNCONFIRMED/CONFIRMED

[Scott Harvey]

As a newcomer, I didn't realize I was allowed to change UNCO to CONF and
did so only when absolutely positive the issue existed. But I've already
seen issues like a user who continually reports bugs (often enough that I
recognize the name from among thousands).

When I triage something and find it confirmed, I try to report all the
details of my system and the methods I used to recreate the problem.

Maybe all we need is a little more education and advice for users. Maybe a
popup when changing UNCO to CONF that reads "By doing this, you're going to
alert the very busy development team that you've confirmed a bug in
<product X>. Are you positive you want to do this? Please think it through
before continuing."

Or nicer words to the same effect.


On Tue, Feb 27, 2018 at 6:43 AM, Boudewijn Rempt <boud at valdyas.org> wrote:

> On Tuesday, 27 February 2018 13:30:12 CET Paul Brown wrote:
>
> > Is it true that users get confused by the bugtracking system? If so,
> this is
> > an issue, right?
>
> Well, users can get confused by _everything_. Though I probably have more
> absolutely non-technical users reporting bugs than most other KDE
> projects. I
> haven't seen many signs of users being confused by UNCONFIRMED vs
> CONFIRMED,
> though.
>
> I'm all for making the initial reporting of bugs as smooth as possible for
> users... Though really, I don't need any more bug reports. And after that,
> giving me more information when I ask for it, that would be useful as well.
>
> * It would be useful if users could embed images and videos instead of
> creating attachments.
> * It would be useful if users could use rich text in their reports.
> * It would be useful if users could sign in with their cloud identities
> (horrible though that idea is).
> * It would be useful if bugzilla and the forum used the same login.
> * It would even be useful if we could add badges or something like that to
> tell the reporter "thank you for your report" with a nice graphic
>
> But messing with the statuses that basically define the workflow for the
> developer because we think that users will feel happier seeing NEW than
> UNCONFIRMED doesn't sound too useful to me.
>
> If we want to change that, let's change it in a way that will support
> people
> triaging a thousand bugs or so a year.
>
> --
> Boudewijn Rempt | https://www.valdyas.org | https://www.krita.org
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-community/attachments/20180227/7cd5d47f/attachment.htm>