Re: Let's get rid of UNCONFIRMED/CONFIRMED

On Tue, 10 Apr 2018 10:29:54 -0700 Albert Astals Cid wrote > Of course it makes sense for wishlists to be confirmed. > > OPEN -> Nobody's looked at it yet > CONFIRMED -> Somebody looked at it and is a wish that makes sense. A "confirmed" status only makes

Re: Let's get rid of UNCONFIRMED/CONFIRMED

On dinsdag 10 april 2018 18:10:00 CEST tetris4 wrote: > Hi all, > > Sorry for bumping an old thread. I'm responsible for the Streamlined > Onboarding goal and Bugzilla seems to be a hot topic relating to this. This > is already the second thread I'm posting this message, the first one being >

Re: Let's get rid of UNCONFIRMED/CONFIRMED

We have a thread where someone proposes removing statuses, and a proposal which involves adding a status :/ That doesn't sound like we're unified on what we need at all. ​Personally I would use flags for this "reproducible" or not. Advantages are: - it visibly lists who could reproduce it in a

Re: Let's get rid of UNCONFIRMED/CONFIRMED

Adriaan de Groot ha scritto: > On Tuesday, 10 April 2018 19:18:07 CEST, Nate Graham wrote: >> OPEN -> Nobody's looked at it yet >> TRIAGED -> Somebody looked at it but couldn't reproduce it yet >> CONFIRMED -> Somebody looked at it and was able to reproduce it >> > > Is bugzilla really that hard

Re: Let's get rid of UNCONFIRMED/CONFIRMED

On Tue, 10 Apr 2018 10:50:19 -0700 Albert Astals Cid wrote > El dimarts, 10 d’abril de 2018, a les 19:43:51 CEST, Nate Graham va > escriure: > > On Tue, 10 Apr 2018 10:29:54 -0700 Albert Astals Cid > > wrote > > > Of course it makes

Re: Let's get rid of UNCONFIRMED/CONFIRMED

El dimarts, 10 d’abril de 2018, a les 19:43:51 CEST, Nate Graham va escriure: > On Tue, 10 Apr 2018 10:29:54 -0700 Albert Astals Cid > wrote > > Of course it makes sense for wishlists to be confirmed. > > > > OPEN -> Nobody's looked at it yet > > CONFIRMED -> Somebody

Re: Let's get rid of UNCONFIRMED/CONFIRMED

On Tue, 10 Apr 2018 10:29:54 -0700 Albert Astals Cid wrote > Of course it makes sense for wishlists to be confirmed. > > OPEN -> Nobody's looked at it yet > CONFIRMED -> Somebody looked at it and is a wish that makes sense. A "confirmed" status only makes

Re: Let's get rid of UNCONFIRMED/CONFIRMED

On Tuesday, 10 April 2018 19:18:07 CEST, Nate Graham wrote: OPEN -> Nobody's looked at it yet TRIAGED -> Somebody looked at it but couldn't reproduce it yet CONFIRMED -> Somebody looked at it and was able to reproduce it Is bugzilla really that hard to configure with a workflow? I ran into

Re: Let's get rid of UNCONFIRMED/CONFIRMED

El dimarts, 10 d’abril de 2018, a les 19:18:07 CEST, Nate Graham va escriure: > I'll jump in too. > > I think it's important to mention that Bugzilla is not purely a developer > tool: it's an interface between developers and users. We can't neglect the > user experience in favor of the developer

Re: Let's get rid of UNCONFIRMED/CONFIRMED

I'll jump in too. I think it's important to mention that Bugzilla is not purely a developer tool: it's an interface between developers and users. We can't neglect the user experience in favor of the developer experience. With thoughtful design, we should be able to handle both without

Re: Let's get rid of UNCONFIRMED/CONFIRMED

On Wednesday, 28 February 2018 08:58:51 CET Ilmari Lauhakangas wrote: > What you need to focus on right now is not bikeshedding about statuses > etc., but to recruit more and more QA/triagers. The QA team is Martin's > "second level support". This is the primary solution. Yeah, I guess this is

Re: Let's get rid of UNCONFIRMED/CONFIRMED

On 28.02.2018 12:01, Luigi Toscano wrote: On Wednesday, 28 February 2018 10:32:58 CET Boudewijn Rempt wrote: On Wednesday, 28 February 2018 00:14:30 CET Luigi Toscano wrote: On bugzilla.redhat.com some teams use the Triaged keyword. I think it would be a good solution. I've been trying that,

Re: Let's get rid of UNCONFIRMED/CONFIRMED

On Wednesday, 28 February 2018 11:01:22 CET Luigi Toscano wrote: > I disagree and I think it makes sense as keyword, as general attribute of > the bug (something happened according a triaging process). It is a modifier > of the "NEW"/initial state that is brought around later. Yours is, of

Re: Let's get rid of UNCONFIRMED/CONFIRMED

On Wednesday, 28 February 2018 10:32:58 CET Boudewijn Rempt wrote: > On Wednesday, 28 February 2018 00:14:30 CET Luigi Toscano wrote: > > On bugzilla.redhat.com some teams use the Triaged keyword. I think it > > would > > be a good solution. > > I've been trying that, and it just doesn't work for

Re: Let's get rid of UNCONFIRMED/CONFIRMED

On Wednesday, 28 February 2018 00:14:30 CET Luigi Toscano wrote: > On bugzilla.redhat.com some teams use the Triaged keyword. I think it would > be a good solution. I've been trying that, and it just doesn't work for me, like I said in my first mail to this thread. It doesn't work because it's

Re: Let's get rid of UNCONFIRMED/CONFIRMED

On 27.02.2018 22:06, Boudewijn Rempt wrote: On Tuesday, 27 February 2018 20:39:31 CET Elvis Angelaccio wrote: Exactly. Also, what Luca said: unconfirmed gives the impression that we don't care about the bug. My point is that confirmed/unconfirmed adds more problems than it solves. Note

Re: Let's get rid of UNCONFIRMED/CONFIRMED

On Dienstag, 27. Februar 2018 23:56:57 CET Boudewijn Rempt wrote: > On Tuesday, 27 February 2018 23:17:02 CET Elvis Angelaccio wrote: > > On martedì 27 febbraio 2018 21:06:04 CET, Boudewijn Rempt wrote: > > > On Tuesday, 27 February 2018 20:39:31 CET Elvis Angelaccio wrote: > > >> Exactly. Also,

Re: Let's get rid of UNCONFIRMED/CONFIRMED

On Tuesday, 27 February 2018 23:17:02 CET Elvis Angelaccio wrote: > On martedì 27 febbraio 2018 21:06:04 CET, Boudewijn Rempt wrote: > > On Tuesday, 27 February 2018 20:39:31 CET Elvis Angelaccio wrote: > >> Exactly. Also, what Luca said: unconfirmed gives the impression that we > >> don't care

Re: Let's get rid of UNCONFIRMED/CONFIRMED

On martedì 27 febbraio 2018 21:06:04 CET, Boudewijn Rempt wrote: On Tuesday, 27 February 2018 20:39:31 CET Elvis Angelaccio wrote: Exactly. Also, what Luca said: unconfirmed gives the impression that we don't care about the bug. My point is that confirmed/unconfirmed adds more problems than

Re: Let's get rid of UNCONFIRMED/CONFIRMED

On Tuesday, 27 February 2018 22:52:16 CET Elvis Angelaccio wrote: > On martedì 27 febbraio 2018 21:09:12 CET, Boudewijn Rempt wrote: > > On Tuesday, 27 February 2018 20:33:37 CET Elvis Angelaccio wrote: > >> It's confusing also for new developers/triagers. Yesterday a new triager > >> asked me why

Re: Let's get rid of UNCONFIRMED/CONFIRMED

On martedì 27 febbraio 2018 21:09:12 CET, Boudewijn Rempt wrote: On Tuesday, 27 February 2018 20:33:37 CET Elvis Angelaccio wrote: It's confusing also for new developers/triagers. Yesterday a new triager asked me why I had not set a reproducible bug as confirmed and when he should set the

Re: Let's get rid of UNCONFIRMED/CONFIRMED

On Tuesday, 27 February 2018 20:29:07 CET Martin Flöser wrote: > For KWin at least I would not need the destinction. Every bug is looked > at in less than 24 hours. On the other hand no bug is reproduced till I > try to fix it. And that can take time, sometimes years, sometimes never. Then you

Re: Let's get rid of UNCONFIRMED/CONFIRMED

On Tuesday, 27 February 2018 20:33:37 CET Elvis Angelaccio wrote: > It's confusing also for new developers/triagers. Yesterday a new triager > asked me why I had not set a reproducible bug as confirmed and when he > should set the confirmed status. It's just an unnecessary step which makes > the

Re: Let's get rid of UNCONFIRMED/CONFIRMED

On Tuesday, 27 February 2018 20:39:31 CET Elvis Angelaccio wrote: > Exactly. Also, what Luca said: unconfirmed gives the impression that we > don't care about the bug. > > My point is that confirmed/unconfirmed adds more problems than it solves. Note _again_ that I am NOT asking for keeping

Re: Let's get rid of UNCONFIRMED/CONFIRMED

On martedì 27 febbraio 2018 20:19:24 CET, Martin Flöser wrote: Am 2018-02-27 13:43, schrieb Boudewijn Rempt: 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

Re: Let's get rid of UNCONFIRMED/CONFIRMED

On martedì 27 febbraio 2018 11:41:04 CET, Boudewijn Rempt wrote: On Tuesday, 27 February 2018 11:32:10 CET Elvis Angelaccio wrote: Hi, recently we introduced a policy change in bugzilla and now every user has the power to change the status of any ticket. This is good (and consistent with

Re: Let's get rid of UNCONFIRMED/CONFIRMED

Am 2018-02-27 20:22, schrieb Boudewijn Rempt: On Tuesday, 27 February 2018 20:19:24 CET Martin Flöser wrote: Am 2018-02-27 13:43, schrieb Boudewijn Rempt: > 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, >>

Re: Let's get rid of UNCONFIRMED/CONFIRMED

Am 2018-02-27 20:21, schrieb Boudewijn Rempt: On Tuesday, 27 February 2018 20:15:40 CET Martin Flöser wrote: As KWin has the same problem as Krita I can also answer. In the case of KWin about 90 % of the incoming bug reports is not a bug, but either duplicate, driver crash, useless crash

Re: Let's get rid of UNCONFIRMED/CONFIRMED

On Tuesday, 27 February 2018 20:19:24 CET Martin Flöser wrote: > Am 2018-02-27 13:43, schrieb Boudewijn Rempt: > > 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,

Re: Let's get rid of UNCONFIRMED/CONFIRMED

On Tuesday, 27 February 2018 20:15:40 CET Martin Flöser wrote: > > As KWin has the same problem as Krita I can also answer. In the case of > KWin about 90 % of the incoming bug reports is not a bug, but either > duplicate, driver crash, useless crash reports from Arch users or user > support

Re: Let's get rid of UNCONFIRMED/CONFIRMED

Am 2018-02-27 14:45, schrieb Paul Brown: On Tuesday, 27 February 2018 13:43:17 CET Boudewijn Rempt 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

Re: Let's get rid of UNCONFIRMED/CONFIRMED

Am 2018-02-27 13:43, schrieb Boudewijn Rempt: 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

Re: Let's get rid of UNCONFIRMED/CONFIRMED

Am 2018-02-27 12:22, schrieb Paul Brown: On Tuesday, 27 February 2018 11:51:42 CET Boudewijn Rempt wrote: On Tuesday, 27 February 2018 11:47:22 CET Paul Brown wrote: > On Tuesday, 27 February 2018 11:41:04 CET Boudewijn Rempt wrote: > > Given that bugzilla is a tool for developers, I don't care

Re: Let's get rid of UNCONFIRMED/CONFIRMED

On Tue, Feb 27, 2018 at 11:32 PM, Elvis Angelaccio wrote: > Hi, Hi Elvis, > recently we introduced a policy change in bugzilla and now every user has > the power to change the status of any ticket. > > This is good (and consistent with phabricator) but there is a big

Re: Let's get rid of UNCONFIRMED/CONFIRMED

On Tuesday, 27 February 2018 15:03:02 CET Ilmari Lauhakangas wrote: > I don't think it's relevant to ask Boud to start some huge Bugzilla user > experience revamp on top of the things he is already dealing with. Sorry for the confusion. I was using the royal "you", that is, referring to

Re: Let's get rid of UNCONFIRMED/CONFIRMED

On Tuesday, 27 February 2018 15:23:16 CET Luca Beltrame wrote: > Il giorno Tue, 27 Feb 2018 14:58:22 +0100 > Boudewijn Rempt ha > > scritto: > > * A bug nobody has looked at yet > > How would NEW not fit the bill? (As opposed to UNCONFIRMED) > > > * A bug someone other than

Re: Let's get rid of UNCONFIRMED/CONFIRMED

Il giorno Tue, 27 Feb 2018 14:58:22 +0100 Boudewijn Rempt ha scritto: > * A bug nobody has looked at yet How would NEW not fit the bill? (As opposed to UNCONFIRMED) > * A bug someone other than the reporter has looked at, but which was > not reproducible Do you mean a single

Re: Let's get rid of UNCONFIRMED/CONFIRMED

On 27.02.2018 15:45, Paul Brown wrote: On Tuesday, 27 February 2018 13:43:17 CET Boudewijn Rempt 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

Re: Let's get rid of UNCONFIRMED/CONFIRMED

On Tuesday, 27 February 2018 14:45:51 CET Paul Brown wrote: > On Tuesday, 27 February 2018 13:43:17 CET Boudewijn Rempt 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,

Re: Let's get rid of UNCONFIRMED/CONFIRMED

On Tuesday, 27 February 2018 13:43:17 CET Boudewijn Rempt 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_. If a service is

Re: Let's get rid of UNCONFIRMED/CONFIRMED

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

Re: Let's get rid of UNCONFIRMED/CONFIRMED

Il giorno Tue, 27 Feb 2018 13:43:17 +0100 Boudewijn Rempt ha scritto: > KDE projects. I haven't seen many signs of users being confused by > UNCONFIRMED vs CONFIRMED, though. At least in certain forums (not necessarily the KDE forums, this includes media like reddit),

Re: Let's get rid of UNCONFIRMED/CONFIRMED

On Tuesday, 27 February 2018 13:28:50 CET Boudewijn Rempt wrote: > I thought I was clear enough, users should report bugs in bugs.kde.org. They > should not report bugs anywhere else. Not on phabricator, the forum, > reddit, twitter, tumblr, devianart, blenderartists, google+, facebook or >

Re: Let's get rid of UNCONFIRMED/CONFIRMED

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

Re: Let's get rid of UNCONFIRMED/CONFIRMED

On Tuesday, 27 February 2018 13:16:03 CET Aleix Pol wrote: > On Tue, Feb 27, 2018 at 12:22 PM, Paul Brown wrote: > > On Tuesday, 27 February 2018 11:51:42 CET Boudewijn Rempt wrote: > >> On Tuesday, 27 February 2018 11:47:22 CET Paul Brown wrote: > >> > On Tuesday, 27 February

Re: Let's get rid of UNCONFIRMED/CONFIRMED

On Tuesday, 27 February 2018 12:22:51 CET you wrote: > On Tuesday, 27 February 2018 11:51:42 CET Boudewijn Rempt wrote: > > On Tuesday, 27 February 2018 11:47:22 CET Paul Brown wrote: > > > So... where are users supposed to report bugs? > > > > Users report bugs in bugs.kde.org. > > I'll ask

Re: Let's get rid of UNCONFIRMED/CONFIRMED

On Tue, Feb 27, 2018 at 12:22 PM, Paul Brown wrote: > On Tuesday, 27 February 2018 11:51:42 CET Boudewijn Rempt wrote: >> On Tuesday, 27 February 2018 11:47:22 CET Paul Brown wrote: >> > On Tuesday, 27 February 2018 11:41:04 CET Boudewijn Rempt wrote: >> > > Given that

Re: Let's get rid of UNCONFIRMED/CONFIRMED

On Tuesday, 27 February 2018 11:51:42 CET Boudewijn Rempt wrote: > On Tuesday, 27 February 2018 11:47:22 CET Paul Brown wrote: > > On Tuesday, 27 February 2018 11:41:04 CET Boudewijn Rempt wrote: > > > Given that bugzilla is a tool for developers, I don't care that users > > > might > > > get

Re: Let's get rid of UNCONFIRMED/CONFIRMED

On Tuesday, 27 February 2018 11:47:22 CET Paul Brown wrote: > On Tuesday, 27 February 2018 11:41:04 CET Boudewijn Rempt wrote: > > Given that bugzilla is a tool for developers, I don't care that users > > might > > get confused. > > > > > We don't have this problem with phabricator tasks because

Re: Let's get rid of UNCONFIRMED/CONFIRMED

Il giorno Tue, 27 Feb 2018 11:32:10 +0100 Elvis Angelaccio ha scritto: > The UNCONFIRMED/CONFIRMED thing has little meaning, is confusing for > users and for new triagers and we know that many developers never set +1 On setting it to NEW. That's what we have in

Re: Let's get rid of UNCONFIRMED/CONFIRMED

On Tuesday, 27 February 2018 11:41:04 CET Boudewijn Rempt wrote: > Given that bugzilla is a tool for developers, I don't care that users might > get confused. > > > We don't have this problem with phabricator tasks because they can be > > either Open or closed (for whatever reason). > > I don't

Re: Let's get rid of UNCONFIRMED/CONFIRMED

On Tuesday, 27 February 2018 11:32:10 CET Elvis Angelaccio wrote: > Hi, > recently we introduced a policy change in bugzilla and now every user has > the power to change the status of any ticket. > > This is good (and consistent with phabricator) but there is a big downside: > many people will

Let's get rid of UNCONFIRMED/CONFIRMED

Hi, recently we introduced a policy change in bugzilla and now every user has the power to change the status of any ticket. This is good (and consistent with phabricator) but there is a big downside: many people will open a new ticket and then mark it as CONFIRMED. This is annoying because