<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 30. 7. 2016, at 2:30, Alexey Kazakov <<a href="mailto:alkazako@redhat.com" class="">alkazako@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="content-type" content="text/html; charset=utf-8" class=""><div dir="auto" class=""><div class="">I think we should grant reviewer access to all members of jbosstools org. For example QE may not have push access in github but we still want them be able to create issues based on aeri reports.</div></div></div></blockquote><div><br class=""></div>I agree :) So can you make it happen please, Marcel?</div><div><br class=""></div><div>Thanks,</div><div>Martin</div><div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div dir="auto" class=""><div class="">Regarding links in jira... Ideally the same link should work for everyone with optional GitHub authentication. If you do not login or you are not a jbosstools org member you see a public version of the report. Otherwise you see what you are supposed to see corresponding to your role. </div><div class="">If it requires significant efforts to implement then can we post a few links for different roles with clear descriptions as a workaround?</div><div class=""><br class=""></div><div class="">WDYT?</div><div class=""><br class=""></div><div class=""><br class="">On Jul 28, 2016, at 6:32 AM, Marcel Bruch <<a href="mailto:marcel.bruch@codetrails.com" class="">marcel.bruch@codetrails.com</a>> wrote:<br class=""><br class=""></div><blockquote type="cite" class=""><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On 28 Jul 2016, at 15:00, Martin Malina <<a href="mailto:mmalina@redhat.com" class="">mmalina@redhat.com</a>> wrote:</div><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">In my opinion, it would make sense to just give the reporter role to the whole jbosstools team on github. </div></div></div></blockquote><br class=""></div><div class="">Just a minor correction:</div><div class=""><br class=""></div><div class="">We use different URL prefixes for reviewers and reporters. If a “reporter" accesses a “reviewer" url, he/she gets an "access denied”. That’s what you got when clicking on a JIRA link.</div><div class=""><br class=""></div><div class="">The different url prefixes were required in previous versions of AERI. We could, however, change the current system to use only one url and so that <b class="">*all* reporters</b> get a <b class="">public/anonymized view of a problem</b>. Please note the word anonymized. Problems may contain senstive information like email addresses, error messages etc. We thus cannot make them public available to everyone as-is.</div><div class=""><br class=""></div><div class="">However, at Eclipse we agreed on showing a anonymized view might be perfectly okay. So we could do the same here.</div><div class=""><br class=""></div><div class="">Max, Alexey, Fred,</div><div class="">what do you think?</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div></div></blockquote><blockquote type="cite" class=""><div class=""><span class="">_______________________________________________</span><br class=""><span class="">jbosstools-dev mailing list</span><br class=""><span class=""><a href="mailto:jbosstools-dev@lists.jboss.org" class="">jbosstools-dev@lists.jboss.org</a></span><br class=""><span class=""><a href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev" class="">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a></span></div></blockquote></div></div></blockquote></div><br class=""></body></html>