[Libreoffice-qa] Bug Report Incorrectly Marked as NEW

2013-06-14 Thread Michael Chen
Hello, I reported a bug, which is located at https://bugs.freedesktop.org/show_bug.cgi?id=65571 . However, it is marked as NEW even though no one triaged it. Can someone resolve this? Thanks. ___ List Name: Libreoffice-qa mailing list Mail address: Lib

Re: [Libreoffice-qa] Bug Report Incorrectly Marked as NEW

2013-06-14 Thread Pedro
. If additional information is required it will be changed to NEEDINFO. I'm not sure what a triager should change it to if it is confirmed... @Joel??? -- View this message in context: http://nabble.documentfoundation.org/Libreoffice-qa-Bug-Report-Incorrectly-Marked-as-NEW-tp4061545p4061555.h

Re: [Libreoffice-qa] Bug Report Incorrectly Marked as NEW

2013-06-14 Thread Florian Reisinger
it will be changed to NEEDINFO. I'm not sure what a > triager should change it to if it is confirmed... @Joel??? > > > > -- > View this message in context: > http://nabble.documentfoundation.org/Libreoffice-qa-Bug-Report-Incorrectly-Marked-as-NEW

Re: [Libreoffice-qa] Bug Report Incorrectly Marked as NEW

2013-06-15 Thread Christian Lohmaier
Hi Florian, *, On Sat, Jun 15, 2013 at 6:34 AM, Florian Reisinger wrote: > > Pedro is it true, that this has changed? IMHO we had this nasty > problem once, but IMO all new bugs should be UNCONFIRMED. Bugs reported via the BugAssistant should be UNCONFIRMED, but the default when creating bugs on

Re: [Libreoffice-qa] Bug Report Incorrectly Marked as NEW

2013-06-15 Thread Florian Reisinger
Hi, Liebe Grüße, / Yours, Florian Reisinger Am 15.06.2013 um 14:50 schrieb Christian Lohmaier : > Hi Florian, *, > > On Sat, Jun 15, 2013 at 6:34 AM, Florian Reisinger wrote: >> >> Pedro is it true, that this has changed? IMHO we had this nasty >> problem once, but IMO all new bugs should be UN

Re: [Libreoffice-qa] Bug Report Incorrectly Marked as NEW

2013-06-15 Thread Stephan Bergmann
On 06/15/2013 02:52 PM, Florian Reisinger wrote: Am 15.06.2013 um 14:50 schrieb Christian Lohmaier : On Sat, Jun 15, 2013 at 6:34 AM, Florian Reisinger wrote: Pedro is it true, that this has changed? IMHO we had this nasty problem once, but IMO all new bugs should be UNCONFIRMED. Bugs report

Re: [Libreoffice-qa] Bug Report Incorrectly Marked as NEW

2013-06-15 Thread Florian Reisinger
Hi Am 15.06.2013 15:18, schrieb Stephan Bergmann: On 06/15/2013 02:52 PM, Florian Reisinger wrote: Am 15.06.2013 um 14:50 schrieb Christian Lohmaier : On Sat, Jun 15, 2013 at 6:34 AM, Florian Reisinger wrote: Pedro is it true, that this has changed? IMHO we had this nasty problem once, but I

Re: [Libreoffice-qa] Bug Report Incorrectly Marked as NEW

2013-06-15 Thread Christian Lohmaier
Hi Florian, *, On Sat, Jun 15, 2013 at 2:52 PM, Florian Reisinger wrote: > Am 15.06.2013 um 14:50 schrieb Christian Lohmaier > : >> On Sat, Jun 15, 2013 at 6:34 AM, Florian Reisinger >> wrote: >>> >>> Pedro is it true, that this has changed? IMHO we had this nasty >>> problem once, but IMO all

Re: [Libreoffice-qa] Bug Report Incorrectly Marked as NEW

2013-06-15 Thread Terrence Enger
On Sat, 2013-06-15 at 15:41 +0200, Florian Reisinger wrote: > > It should be unconfirmed as long as someone from the QA team (so > everyone triaging) can reproduce it on his machine, preferably on a > different OS Well, I usually do not file a bug until I am pretty sure that I am seeing wha

Re: [Libreoffice-qa] Bug Report Incorrectly Marked as NEW

2013-06-15 Thread mariosv
://nabble.documentfoundation.org/Libreoffice-qa-Bug-Report-Incorrectly-Marked-as-NEW-tp4061545p4061556.html Sent from the QA mailing list archive at Nabble.com. ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings

Re: [Libreoffice-qa] Bug Report Incorrectly Marked as NEW

2013-06-17 Thread Cor Nouws
Christian Lohmaier wrote (15-06-13 16:21) bugs filed should be unconfirmed by default (but user can change to NEW when filing a bug) (and are unconfirmed by default, at least with my privileges) And AFAIK every bugzilla user on fdo has "canconfirm" privileges. In general, when I file a bug (al