I don't think it was QE - but - I was out all last week - maybe someone did
something.... ;-)
On Mon, Jul 11, 2016 at 1:00 PM, Alexey Kazakov <alkazako(a)redhat.com> wrote:
On 07/11/2016 12:49 PM, George Gastaldi wrote:
Thanks Alexey,
The issues I was referring to were:
<
https://issues.jboss.org/browse/JBIDE-22705>
https://issues.jboss.org/browse/JBIDE-22705 and
https://issues.jboss.org/browse/JBIDE-22706
I don't remember creating those issues through the web interface, perhaps
someone else did it?
Maybe someone from QE?
Anyway, I was just wondering if there is some way to have the user steps
used to reproduce those exceptions from AERI, otherwise I'll just close
them as Cannot Reproduce.
If these exceptions do not reported often and you don't see what could be
the reason for that then I'm not sure there is something we can do with
such reports.
But if they are reported often by different users then it worth a deep
investigation.
Marcel, is there any way to interact with reporters after submitting a
report?
Thanks.
Thank you
*George Gastaldi*
https://onename.com/gastaldi
On Mon, Jul 11, 2016 at 1:44 PM, Alexey Kazakov <alkazako(a)redhat.com>
wrote:
> George, AFAIK these JIRAs are not created automatically. If you see a
> JIRA created by AERI then someone created it via AERI web interface when
> reviewing reports.
> And as Len said, every component lead is supposed to review the reports
> weekly and create JIRAs/close reports for his/her components.
> If you someone doesn't have access to AERI then please let us know.
>
> On 07/11/2016 12:34 PM, Leonard Dimaggio wrote:
>
> I thought that we had agreed that Dev + QE component leads would review
> the (weekly) reports from AERI and then log JIRAs....selectively.
>
> -- Len
>
> On Mon, Jul 11, 2016 at 12:22 PM, George Gastaldi < <ggastald(a)redhat.com>
> ggastald(a)redhat.com> wrote:
>
>> Hi,
>>
>> I noticed that the AERI bot opens some JIRA according to the issues
>> reported by the users. I am having a hard time trying to reproduce these
>> errors, mostly because I don't know what the user did to make that happen.
>> How can I have access to the steps performed by the user when the error
>> occurred?
>>
>> I think that opening an issue with a Stacktrace is not that useful if
>> you don't know how to reproduce that error locally.
>>
>> Best Regards,
>>
>> *George Gastaldi*
>>
>> <
https://onename.com/gastaldi>https://onename.com/gastaldi
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>
>
>
> --
> Len DiMaggio ( <ldimaggi@redhat.com>ldimaggi(a)redhat.com)
> JBoss by Red Hat
> 314 Littleton Road
> Westford, MA 01886 USA
> tel: 978.392.3179
> cell: 781.472.9912
>
http://www.redhat.com
>
http://community.jboss.org/people/ldimaggio
>
>
>
>
> _______________________________________________
> jbosstools-dev mailing
listjbosstools-dev@lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
>
--
Len DiMaggio (ldimaggi(a)redhat.com)
JBoss by Red Hat
314 Littleton Road
Westford, MA 01886 USA
tel: 978.392.3179
cell: 781.472.9912