For me both the request reopening and the create bug report idea
sounds fine. This way there won't any point in time where the user
would feel stuck how to give feedback. Which is - if I understand
correctly - the purpose of the AERI project.
Anyway, thanks for the feedback and also thanks for the
There is nothing yet that allows a normal user to reopen a problem. There are
other means like auto actions that can reopen a problem as soon as a new
incident arrives that shows an already closed error still exists in a newer
version of Buildship. See [1] for an example.
However, we (the Archi
I'm just trying to understand the workflow here. Let's say as an
Eclipse user I enconunter an exception and I report it via AERI. For
some cases I might get the response that this issues was resolved as
invalid (no bug reports involved). Now, what if I know it is not true
and I have an example exhi
At the moment, they would have to put comment on / reopen the bug in Bugzilla.
Would you like to have something "more interactive” or a different behavior?
If so, let me know what you would like to see.
FWIW,
AERI can (in general) reopen bugs in Bugzilla.
Cheers,
Marcel
> On 27 Jul 2016, at 1
Hi Marcel,
Just a quick question: what if a reviewer incorreclty closes a report?
Is there a way for a reporter to reopen it if they are unhappy with
the resolution?
Cheers,
--
Donát Csikós
Software Engineer
Gradle GmbH
Firmensitz: Manteuffelstr. 60, 10999 Berlin, Germany
Registergericht: Amtsg
Greetings Cross-Projects,
a question that was raised by several committers (and I think might be relevant
to some of you as well) was, how to configure AERI to automatically create
Bugzillas from your error reports. I published a short blog post describing how
projects can configure this behavi
