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 <mailto:ggastald@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 _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org <mailto:jbosstools-dev@lists.jboss.org> https://lists.jboss.org/mailman/listinfo/jbosstools-dev -- Len DiMaggio (ldimaggi(a)redhat.com <mailto:ldimaggi@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 list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

Thanks Alexey, The issues I was referring to were: 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?

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.

Thank you *George Gastaldi* https://onename.com/gastaldi On Mon, Jul 11, 2016 at 1:44 PM, Alexey Kazakov <alkazako(a)redhat.com <mailto:alkazako@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 <mailto:ggastald@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 > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev(a)lists.jboss.org > <mailto:jbosstools-dev@lists.jboss.org> > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > > > > > -- > Len DiMaggio (ldimaggi(a)redhat.com <mailto:ldimaggi@redhat.com>) > JBoss by Red Hat > 314 Littleton Road > Westford, MA 01886 USA > tel: 978.392.3179 <tel:978.392.3179> > cell: 781.472.9912 <tel:781.472.9912> > http://www.redhat.com > http://community.jboss.org/people/ldimaggio > > > > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev(a)lists.jboss.org > <mailto:jbosstools-dev@lists.jboss.org> > https://lists.jboss.org/mailman/listinfo/jbosstools-dev

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&gt; 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&gt; > 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@redhat.com&gt;ggastald(a)redhat.com&gt; 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&gt;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 http://www.redhat.com http://community.jboss.org/people/ldimaggio _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

On 11 Jul 2016, at 19:00, Alexey Kazakov <alkazako(a)redhat.com&gt; wrote: Marcel, is there any way to interact with reporters after submitting a report? Yes. Multiple ways. 1. If the reporter left an email address, you can contact them by email. See the “Contact X reporters…” link on the “reporters” panel on the problem page. This, however, only makes sense when the problem is relatively new b/c users usually can’t remember what they did 4 weeks in the past to (re)produce the error. 2. If a problem is turned into a bug report, there is a checkbox whether to inform all reporters about the newly crelated bug report. If the comment in Jira states something like “need steps to reproduce”, users may help. In addition, every new reporter will be pointed to this bug report when he/she experiences this problem on his machine. This increases the likelihood that a user provides further details (but after the bug is created). 3. Set the problem resolution (w/ or w/o JIRA ticket) to “cannot reproduce” and set an additional “custom resolution message”. These messages are displayed to new users when the submit an error report that matched this problem. 4. Set one (or more) needinfo flags. Problems tagged with needinfo are more displayed differently / attract the users attention with special icons etc.: FWIW, the next version of the error reporter will offer a rich feature-set of needinfo flags for different purposes. E.g. for classloading problems AERI will run a local classpath analysis *before submission* and attach it to the error report and a few things more. I’ll send a longer description later this week. For now, I’d go with approach 3, “close" with “cannot reproduce”. If you wish, I can prepare a monthly email digests that summarizes all those problems in a separate email for further review. I can also set up an automated action that “reopens" these problems whenever a new user comment arrives. WDYT? Marcel

If you wish, I can prepare a monthly email digests that summarizes all those problems in a separate email for further review.

I can also set up an automated action that “reopens" these problems whenever a new user comment arrives. WDYT?

Marcel

> On 11 Jul 2016, at 18:44, Alexey Kazakov <alkazako(a)redhat.com&gt; wrote: > > George, AFAIK these JIRAs are not created automatically. Correct. Although the automated error reporter *can* automatically create JIRA tickets (e.g. when certain thresholds like number of reporters > 10) are reached, there is no such rule active for JBoss tools yet. At Eclipse we have a login per user (not a one-for-all login as for JBoss tools). There we append a footer “This bug report was created on behalf of <username>”. For JBoss we’d need to set up a comparable authentication mechanism. Preferably one that works well for all committers and does not require creating yet another account. Is there such system which we could use to authenticate your committers against? Marcel